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

quirky-tokennpm

Advisory published Updated

quirky-token is a confirmed malicious npm package (MAL-2026-6066) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in quirky-token (npm)

MAL-2026-6066
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall quirky-token

What this malware does

The package is advertised as an SVG sanitizer but exposes an undocumented getPlugin() export whose returned function fetches JSON from https://www.jsonkeeper.com/b/3P9BF and passes the response's model field directly to eval(). jsonkeeper.com is an anonymous, mutable paste host with no pinning, hash, or signature — whoever controls that paste can execute arbitrary JavaScript in the consumer's Node.js process whenever the returned function is invoked. The malicious block in index.js is appended below a plausible SVG sanitizer/minifier implementation that serves as cover, and both the HTTP error branch and the eval try/catch are empty so failures are silently swallowed. This is a classic dropper pattern: benign cover code, undocumented export, fetch-and-eval from a mutable third-party paste, concealment of errors. Any consumer who imports this package and calls getPlugin() grants the paste operator full RCE on the importer's host.

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

3 flagged
1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

b263413912feb72882ee0b52e7025c636ed98472ba90e6db4714b3b111b4e2e8
a414b00c83b6fd328d241e0e54f8289cb894be1907656b79df3c2ab6f2bf8537
bacc77e746838c6cb40f40c42cb4bea12f0789f71055c891ceebf7a5e4ad2b5c
4693ac90e019c862e43807d5326753f2abaf4595b4f1f27c5c8a1db103334e57
463f6e3fd7f9bb3a7909e80c26d2af0b036391bc4afdd20cd0e876ca54012970

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for quirky-token (3 malicious versions).

  2. If you installed it — respond

    Remove quirky-token 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.

  3. Did it already run?

    If quirky-token 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. quirky-token on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006904IN-MAL-2026-007030IN-MAL-2026-007029GHSA-8p89-7m4q-45qm

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks quirky-token-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

quirky-token (npm) malicious package — MAL-2026-6066 | O3 Security