Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in abuden5

The npm package abuden5 contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • abuden5

The npm package abuden5 was found to contain malware. According to the GitHub Advisory (GHSA-rjqp-h5m7-gwmr), any computer that has this package installed or running should be considered fully compromised.

The advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, as the attacker may have gained full control of the system.

Users should assume complete system compromise and take appropriate incident response measures.

Indicators of compromise

Packages
  • abuden5

Remediation

  • Immediately isolate any computer that has abuden5 installed or running from the network
  • Rotate all secrets, API keys, credentials, and signing keys from a different, uncompromised computer
  • Remove the abuden5 package from the system
  • Perform a full forensic analysis and malware scan of affected systems
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider the system fully compromised and plan for complete rebuild if critical systems are affected

Sources

  1. GitHub Advisory GHSA-rjqp-h5m7-gwmr · GitHub Advisory Database

Cite this entry

"Malware in abuden5." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 13, 2026; last updated July 13, 2026. https://supplychainattack.org/incident/malware-in-abuden5-5ri1q4

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