Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in nonexistent-package

Malware discovered in the npm package nonexistent-package. Systems with this package installed are considered fully compromised and require immediate remediation.

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

A malicious npm package named nonexistent-package has been identified and published to the npm registry. The package contains malware that grants full control of affected systems to an outside entity.\n\nAny computer with this package installed or running should be considered fully compromised. The advisory recommends immediate rotation of all secrets and keys from a different, uncompromised computer.\n\nWhile the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise achieved by the malware. Full system remediation may be necessary.\n\nThis incident was disclosed via GitHub Advisory GHSA-wxvr-4mc8-3qvj on 2026-07-07.

Indicators of compromise

Packages
  • nonexistent-package

Remediation

  • Immediately remove the nonexistent-package from all systems
  • Rotate all secrets, API keys, and credentials from a clean, uncompromised computer
  • Assume full system compromise and consider complete OS reinstallation
  • Audit all systems for signs of unauthorized access or lateral movement
  • Review logs for any suspicious activity on affected systems
  • Monitor for any data exfiltration or unauthorized access attempts

Sources

  1. GitHub Advisory GHSA-wxvr-4mc8-3qvj · GitHub Advisory Database

Cite this entry

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

Suggest a correction

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

  1. activecritical

    Malware in some-theme

    Malware discovered in the npm package some-theme. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.

    npmCompromised package
  2. containedcritical

    Malware in anthropic-toolkit

    Malware was discovered in the npm package anthropic-toolkit. Systems with this package installed are considered fully compromised and require immediate remediation.

    npmCompromised package
  3. containedcritical

    Malware in brunomenozzi-test-pkg

    Malware was discovered in the npm package brunomenozzi-test-pkg. Systems with this package installed or running should be considered fully compromised and require immediate remediation.

    npmCompromised package
  4. resolvedcritical

    Malware in harmony-enablers-test-2026

    Malware was discovered in the npm package harmony-enablers-test-2026. Systems with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a separate computer.

    npmCompromised package