npm-dc-devnpm
npm-dc-dev is a confirmed malicious npm package (MAL-2026-13378) that executes malicious code on install (malicious version 1.1.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in npm-dc-dev (npm)
What this malware does
package.json declares "postinstall": "node test.js". test.js top-level require('.')s index.js and awaits an exported from_str(). index.js consists of a single Function("k4Wmku", "...") invocation whose ~170KB body is encoded with a custom 85-character alphabet and a shuffled string array; standard deobfuscation does not recover the payload. On npm install, the postinstall hook constructs and runs this opaque code on the installer's machine, with child_process, axios, and form-data available as declared dependencies. Package metadata is generic (blank author and description, name npm-dc-dev) and no legitimate library surface is exported. The install-time construction and execution of an unreadable dynamic payload matches the install-time remote-code-execution pattern; no benign reason exists for this shape.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for npm-dc-dev (version 1.1.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging npm-dc-dev across your stack and pipelines.
If you installed it — respond
Remove npm-dc-dev from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If npm-dc-dev was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks npm-dc-dev before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks npm-dc-dev-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.