MalwarePublished 17 Jun 2026Updated 10 Jul 2026

quirky-token (npm) · Malicious Code

Affects quirky-tokenSource GCVE Database

Malicious package : remove quirky-token and rotate any secrets on hosts that installed it.

Data as of 12 Jul 2026, 11:55 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-6066

What to do

Remove quirky-token from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmquirky-token	Affected =1.0.2 =1.0.1 =1.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The quirky-token npm package contains malicious code hidden behind an undocumented export named getPlugin(). This function fetches JSON data from a mutable third-party paste service and executes the 'model' field using eval(), enabling arbitrary code execution. The package masquerades as an SVG sanitizer but silently swallows errors, concealing its malicious behavior. Any system importing this package and invoking getPlugin() is at risk of full remote code execution by whoever controls the paste. The affected versions are from 1.0.0 through 1.0.2. Removal of the package is recommended, but full system compromise is possible, so all secrets should be rotated.

Impact

Successful exploitation grants the attacker full remote code execution on the host running quirky-token when getPlugin() is called. This leads to complete system compromise, including potential access to all stored secrets and keys. Because the malicious code is fetched dynamically from a mutable external source, the attacker can change the payload at any time, maintaining persistent control. Removal of the package alone does not guarantee eradication of all malicious artifacts or backdoors introduced post-compromise.

Defensive guidance

Users should immediately remove quirky-token versions 1.0.0 through 1.0.2 from their environments. All secrets, credentials, and keys on affected systems must be rotated from a secure, uncompromised machine. Given the high likelihood of full system compromise, consider rebuilding affected hosts from trusted sources. Monitor for any signs of persistent malicious activity.

Summary

quirky-token versions 1.0.0 through 1.0.2 include a malicious backdoor in an undocumented getPlugin() export. This export fetches JSON from https://www.jsonkeeper.com/b/3P9BF, an anonymous and mutable paste hosting service, and directly evaluates the 'model' field with JavaScript eval(). This allows an attacker controlling the paste to execute arbitrary code within the Node.js process of any consumer invoking getPlugin(). The package's main code appears as a legitimate SVG sanitizer, serving as cover. Error handling is intentionally silent, hiding failures and malicious activity. This classic dropper pattern enables full remote code execution on the host running the package. Due to the nature of the compromise, systems with this package installed should be considered fully compromised.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Jul 2026, 11:55 UTC

Technical details

References

Community reviews