Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in true

The npm package 'true' was compromised and distributed with malware. Any computer with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different system.

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

The npm package 'true' was identified as containing malware and distributed to users. According to the GitHub advisory (GHSA-f59f-vj5q-c725), 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 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 compromise.\n\nThis represents a critical supply chain attack through package distribution, affecting the npm ecosystem.

Indicators of compromise

Packages
  • true

Remediation

  • Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the 'true' package from all affected systems
  • Audit system logs for unauthorized access or activity during the period the package was installed
  • Perform a full security assessment of any computer that had this package installed
  • Consider the affected system(s) potentially compromised and plan for full rebuild if critical systems are involved

Sources

  1. GitHub Advisory GHSA-f59f-vj5q-c725 · GitHub Advisory Database

Cite this entry

"Malware in true." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 15, 2026; last updated July 15, 2026. https://supplychainattack.org/incident/malware-in-true-361i96

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