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.

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.

No official patch or fix is currently available. 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. Patch status is not yet confirmed — check the vendor advisory or trusted sources for updates.