Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in leo-streams

Malware was discovered in the npm package leo-streams. 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.

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

The npm package leo-streams was found to contain malware. According to the GitHub Advisory (GHSA-h98v-2hwg-56fx), 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. 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 package installation, as the attacker may have gained full control of the system.\n\nThis is a critical supply chain incident affecting the npm ecosystem.

Indicators of compromise

Packages
  • leo-streams

Remediation

  • Immediately rotate all secrets and keys from a different, uncompromised computer
  • Remove the leo-streams package from all affected systems
  • Conduct a full security audit of any system that had leo-streams installed
  • Review system logs for unauthorized access or modifications
  • Consider full system reimaging if full compromise is suspected
  • Monitor affected systems for signs of persistent malware

Sources

  1. GitHub Advisory GHSA-h98v-2hwg-56fx · GitHub Advisory Database

Cite this entry

"Malware in leo-streams." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 25, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-leo-streams-dc5v4z

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