Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in async-mutex-lock

Malware discovered in the npm package async-mutex-lock. Systems with this package installed are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • async-mutex-lock

The npm package async-mutex-lock has been identified as containing malware. According to the GitHub advisory (GHSA-vwr9-j5fc-42fq), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate rotation of all secrets and keys 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 is a critical supply chain incident affecting the npm ecosystem, with potential for widespread impact across all systems that have installed or are running the affected package."

Indicators of compromise

Packages
  • async-mutex-lock

Remediation

  • Immediately rotate all secrets and keys from a different, uncompromised computer
  • Remove the async-mutex-lock package from all affected systems
  • Conduct a full security audit of any system that had this package installed
  • Review system logs for suspicious activity during the period the package was installed
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved

Sources

  1. GitHub Advisory GHSA-vwr9-j5fc-42fq · GitHub Advisory Database

Cite this entry

"Malware in async-mutex-lock." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 5, 2026; last updated August 5, 2026. https://supplychainattack.org/incident/malware-in-async-mutex-lock-1ikkvl

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 epic-common-node (npm)

    The npm package epic-common-node was found to contain malicious code. The package has been identified and reported through GitHub Security Advisory GHSA-m36g-mhjr-ww2c.

    npmCompromised package
  2. containedcritical

    Malicious code in checkout-desktop-total (npm)

    The npm package checkout-desktop-total contained malicious code that executes a hidden loader on import, downloading and running platform-specific native payloads from attacker-controlled Cloudflare Workers hosts or reconstructing them via DNS TXT records under wel1.ru. Any system that imported this package should be considered compromised.

    npmCompromised package
  3. resolvedcritical

    Malicious code in epic-sso (npm)

    The npm package epic-sso was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.

    npmCompromised package
  4. containedcritical

    Malicious code in epic-common (npm)

    The npm package epic-common was found to contain malicious code. The package was identified by Amazon Inspector and reported through the OpenSSF malicious packages database.

    npmCompromised package