invest-module-cookienpm
invest-module-cookie is a confirmed malicious npm package (MAL-2026-12393) that executes malicious code on install (malicious version 20.8.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in invest-module-cookie (npm)
What this malware does
On require('invest-module-cookie'), index.js loads _adapter.js which selects an OS-specific asset path, downloads an opaque binary from one of three obfuscated *.workers.dev hosts (oob-worker.cf102-baf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf103-070.workers.dev) with a DNS-TXT covert-channel fallback that base64-reassembles chunks from *.dl.well1.site (tin/tina/ldr/win subdomains), writes the payload to /var/tmp or %TEMP% under a disguised name, chmods it 0755, and detaches-spawns it via /bin/sh -c or cmd.exe. Destination hostnames are assembled at runtime from split string fragments (e.g. ['oob-worker.cf102-baf.wo','rkers.dev'].join('')) to defeat static host-scanning. The package is advertised as reusable cookie module components, and the fetched binary bears no relationship to that stated purpose; publisher identity does not match any of the hardcoded hosts.
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 invest-module-cookie (version 20.8.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging invest-module-cookie across your stack and pipelines.
If you installed it — respond
Remove invest-module-cookie 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 invest-module-cookie 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 invest-module-cookie 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 invest-module-cookie-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.