croft-nodenpm
croft-node is a confirmed malicious npm package (MAL-2026-12358) that executes malicious code on install (malicious versions 1.1.2, 1.1.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in croft-node (npm)
What this malware does
package.json declares scripts.postinstall = 'node dist/config.js'. On npm install, dist/config.js performs an outbound fetch to https://my-api.trade-api.workers.dev?id=1 and executes globalThisdata.success using the function name and argument returned by that endpoint. The script also assigns createRequire onto globalThis prior to the dispatch, broadening the set of callable capabilities. The advertised purpose of the package is an in-memory keyed cache with TTL/LRU, which has no need for install-time network I/O; the postinstall behavior is unrelated to the documented library API. The result is remote-controlled code execution on the installer's host at install time, driven by an attacker-controlled Cloudflare Workers endpoint.
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 croft-node (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging croft-node across your stack and pipelines.
If you installed it — respond
Remove croft-node 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 croft-node 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 croft-node 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 croft-node-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.