Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Malware in speed5

The npm package speed5 contained malware that provided full system compromise to attackers. Any computer with the 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
  • speed5

The npm package speed5 was found to contain malware. According to the GitHub Advisory (GHSA-hgpr-8grf-chrq), any computer that has this package installed or running should be considered fully compromised.\n\nThe 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, given that the attacker may have gained full control of the system.\n\nAffected package: speed5 (npm).

Indicators of compromise

Packages
  • speed5

Remediation

  • Immediately isolate any computer that has speed5 installed or running from the network
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the speed5 package from all affected systems
  • Perform a full security audit and malware scan of affected systems
  • Review system logs and access logs for signs of unauthorized activity during the period the package was installed
  • Consider the affected system compromised and plan for full rebuild if critical infrastructure

Sources

  1. GitHub Advisory GHSA-hgpr-8grf-chrq · GitHub Advisory Database

Cite this entry

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

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