registry / Credential exfiltration / npm-dc-dev
npm-dc-dev
This report shows the evidence for npm-dc-dev@1.1.1, the only known version.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe postinstall hook directly triggers heavily obfuscated local-file collection and axios multipart upload code. This is malicious install-time data exfiltration, not package-aligned behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
npm installation runs postinstall, which executes test.js and calls from_str().
Impact
Local browser/profile or other user data can be stolen at install time.
Mechanism
Obfuscated recursive file harvesting and multipart HTTP exfiltration.
Attack narrative
On install, package.json runs test.js, which calls the exported from_str function. In index.js that export launches obfuscated workflows: one derives OS locations, recursively walks and reads files, then packages data with form-data and posts it through axios. The same install-time path also gathers additional local data before upload. The hidden destination does not reduce the confirmed collection-and-exfiltration behavior.
AI rationale
The postinstall hook directly triggers heavily obfuscated local-file collection and axios multipart upload code. This is malicious install-time data exfiltration, not package-aligned behavior.
Evidence
package.jsontest.jsindex.js
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs `node test.js` in postinstall.
- test.js imports and invokes `from_str()` during installation.
- index.js exports an obfuscated `from_str` routine that starts two async workflows.
- index.js imports fs, path, os, child_process, axios, and form-data.
- One workflow recursively enumerates files below OS-derived locations and reads files.
- Read data is assembled into multipart FormData and sent with axios.
Evidence against
- No benign package functionality or documented purpose is present.
- No plaintext endpoint is recoverable without executing the obfuscated payload.
Behavioral surface
Eval
Minified
Source & flagged code
3 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node test.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•Runtime dependency names matching Node built-ins: child_process, os
High
Node Builtin Dependency Squat
Package declares a runtime dependency whose name matches a Node built-in module.
package.jsonView on unpkgindex.jsView file
1Function("k4Wmku","var sPkypnJ,V2cpNzh,eroJJFH,upvIHA1,Y0G4Y6A,PZgX6ef,crMqHTb,hVkooj,TySa_w9,VYSzMa,YHfNIa,U1qLRNz;function eCx9WAp(sPkypnJ,V2cpNzh,eroJJFH){for(eroJJFH=0x0;eroJJF...
Low
Eval
Package source references a known benign dynamic code generation pattern.
index.jsView on unpkg · L1Findings
2 High2 Low
HighInstall Time Lifecycle Scriptspackage.json
HighNode Builtin Dependency Squatpackage.json
LowScripts Present
LowEvalindex.js
Affected versions and remediation
This report applies to npm-dc-dev@1.1.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing npm-dc-dev@1.1.1. 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.