Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in @mp-op-ss-front-lib/tracks

Malware was discovered in the npm package @mp-op-ss-front-lib/tracks. 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
  • @mp-op-ss-front-lib/tracks

A malicious package named @mp-op-ss-front-lib/tracks was published to npm and contains malware. Any computer that has installed or run this package should be considered fully compromised, with potential for complete system takeover by an external entity.\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 initial compromise.\n\nThis incident was disclosed via GitHub Advisory GHSA-rcc9-cq4p-xv77 on 2026-07-31.

Indicators of compromise

Packages
  • @mp-op-ss-front-lib/tracks

Remediation

  • Immediately rotate all secrets, keys, and credentials from a different, uncompromised computer
  • Remove the @mp-op-ss-front-lib/tracks package from all affected systems
  • Perform a full security audit and malware scan on any system that had this package installed
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider full system reimaging if the package was installed on production or sensitive systems

Sources

  1. GitHub Advisory GHSA-rcc9-cq4p-xv77 · GitHub Advisory Database

Cite this entry

"Malware in @mp-op-ss-front-lib/tracks." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 31, 2026; last updated August 1, 2026. https://supplychainattack.org/incident/malware-in-mp-op-ss-front-lib-tracks-edk4xu

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. resolvedcritical

    Malware in test-dev-exec

    The npm package test-dev-exec contained malware that provided full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package
  2. resolvedcritical

    Malware in test-dev-link

    Malware was discovered in the npm package test-dev-link. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.

    npmCompromised package
  3. resolvedcritical

    Malware in @moxfive-llc/common

    Malware was discovered in the npm package @moxfive-llc/common. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.

    npmCompromised package
  4. resolvedcritical

    Malware in test-dev-dispatch

    Malware was discovered in the npm package test-dev-dispatch. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.

    npmCompromised package