Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in paperclip2

Malware was discovered in the npm package paperclip2. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with paperclip2 installed or running is considered fully compromised.
Ecosystems
Attack vectors
Affected entities
  • paperclip2

The npm package paperclip2 has been identified as containing malware. According to the GitHub Advisory (GHSA-27r8-2rjc-75rv), any computer that has this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers should be rotated immediately from a different, uncompromised computer. The package should be removed, though there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise.\n\nGiven the severity of the compromise, affected users should assume full system compromise and take appropriate incident response measures.

Indicators of compromise

Packages
  • paperclip2

Remediation

  • Remove the paperclip2 package immediately from all systems
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Assume full system compromise and conduct thorough incident response
  • Scan affected systems for additional malware or persistence mechanisms
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration

Sources

  1. GitHub Advisory GHSA-27r8-2rjc-75rv · GitHub Advisory Database

Cite this entry

"Malware in paperclip2." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 7, 2026; last updated July 7, 2026. https://supplychainattack.org/incident/malware-in-paperclip2-1ec0gh

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. resolvedcritical

    Malicious code in test2221 (npm)

    The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.

    npmCompromised package
  2. containedcritical

    Malware in n8n-nodes-trust-me-im-totally-safe

    Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.

    npmCompromised package
  3. activecritical

    Malware in litespeed-cache

    Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.

    npmCompromised package
  4. containedcritical

    Malware in open-worker-cli

    Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.

    npmCompromised package