croft-nodenpm
Advisory published Updated
croft-node is a confirmed malicious npm package (MAL-2026-12358) that executes malicious code on install (malicious versions 1.1.1, 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
Search your lockfiles and build artifacts for croft-node (3 malicious versions).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
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.