Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in @mc-xp/mc-monolith-js-src-package

The npm package @mc-xp/mc-monolith-js-src-package contained malware that grants full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different machine.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • @mc-xp/mc-monolith-js-src-package

A malicious npm package, @mc-xp/mc-monolith-js-src-package, was identified as containing malware. According to the GitHub Advisory (GHSA-58vg-vvv2-vr42), 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 machine. While the package should be removed, the advisory notes that because full control of the computer may have been given to an outside entity, there is no guarantee that removing the package alone will remove all malicious software resulting from the installation.\n\nThis represents a critical supply chain attack through a compromised npm package with severe impact on any system that installed it.

Indicators of compromise

Packages
  • @mc-xp/mc-monolith-js-src-package

Remediation

  • Immediately isolate any computer that has installed or run @mc-xp/mc-monolith-js-src-package from the network
  • Rotate all secrets, API keys, credentials, and cryptographic keys from a different, uncompromised computer
  • Remove the @mc-xp/mc-monolith-js-src-package from all systems
  • Perform a full forensic analysis and malware scan on affected systems
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider full system reimaging as the advisory indicates removal may not eliminate all malicious software

Sources

  1. GitHub Advisory GHSA-58vg-vvv2-vr42 · GitHub Advisory Database

Cite this entry

"Malware in @mc-xp/mc-monolith-js-src-package." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-mc-xp-mc-monolith-js-src-package-1s62pb

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