Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in routing-controls

The npm package routing-controls was compromised and distributed with malware. Any system 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
  • routing-controls

The npm package routing-controls was found to contain malware. GitHub Security Advisory GHSA-jmhh-mvpj-27qq documents the incident.\n\nAccording to the advisory, any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on affected computers should be rotated immediately from a different, unaffected system.\n\nWhile the package should be removed, complete remediation cannot be guaranteed due to the potential for the malware to have granted full control of the system to an outside entity, meaning additional malicious software may persist beyond package removal.\n\nAffected package: routing-controls (npm).

Indicators of compromise

Packages
  • routing-controls

Remediation

  • Immediately remove the routing-controls package from all systems
  • Rotate all secrets, keys, and credentials stored on affected computers from a different, unaffected computer
  • Perform a full security audit and malware scan of any system that had the package installed or running
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider the affected system(s) potentially compromised and plan for full rebuild if critical infrastructure

Sources

  1. GitHub Advisory GHSA-jmhh-mvpj-27qq · GitHub Advisory Database

Cite this entry

"Malware in routing-controls." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 11, 2026; last updated June 11, 2026. https://supplychainattack.org/incident/malware-in-routing-controls-8wvnrg

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