Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in wac-atl-context

The npm package wac-atl-context was found to contain malware, resulting in full system compromise of any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.

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

The npm package wac-atl-context was identified as containing malware. According to the GitHub advisory, any computer that has this package installed or running should be considered fully compromised.\n\nAffected systems require immediate remediation. All secrets and keys stored on compromised computers should be rotated immediately from a different, unaffected computer. The malicious package should be removed, though full system compromise means there is no guarantee that package removal alone will eliminate all malicious software that may have been installed.\n\nThis is a critical supply chain incident affecting the npm ecosystem.

Indicators of compromise

Packages
  • wac-atl-context

Remediation

  • Immediately rotate all secrets and keys from a different, unaffected computer
  • Remove the wac-atl-context package from all affected systems
  • Conduct a full security audit of any system that had this package installed
  • Review system logs for unauthorized access or activity during the period the package was installed
  • Consider full system reimaging if the package was installed on production or sensitive systems

Sources

  1. GitHub Advisory GHSA-hx4g-w4gr-x32f · GitHub Advisory Database

Cite this entry

"Malware in wac-atl-context." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-wac-atl-context-1bjiq4

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