Which versions of invest-module-cookie are malicious?

The following npm versions of invest-module-cookie are flagged malicious: 20.8.2. Treat any of these as compromised.

How do I remediate invest-module-cookie if I installed it?

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.

I already installed invest-module-cookie — how do I know if it already compromised me?

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.

Is invest-module-cookie part of a known attack campaign?

Yes — invest-module-cookie is associated with the IN-MAL-2026-014697, GHSA-j5gr-vpx9-45fh campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find invest-module-cookie across my projects, lockfiles, and CI pipelines?

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.

Malicious package

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)

MAL-2026-12393

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall invest-module-cookie

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.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

20.8.2

Indicators of compromise (SHA-256)

6c3f53c4d50d2dedd530c65015b26a902950e6e2bbef3cda3560a661d4aad178

29dfcd241e45bbbefbb5df82057898c212a9e042de6b484de1be7f2347cf7f01

Detection & response playbook

Malicious package

Find 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

No. invest-module-cookie on npm has been identified as a malicious package (version 20.8.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014697GHSA-j5gr-vpx9-45fh

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database