Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in @monitoring-lib/error-tracking

Malware discovered in the npm package @monitoring-lib/error-tracking. 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
  • @monitoring-lib/error-tracking

A malicious version of the npm package @monitoring-lib/error-tracking has been identified and published to the npm registry. The package contains malware that grants full control of affected systems to an outside entity.\n\nAny computer with this package installed or running should be considered fully compromised. The malware may have provided attackers with complete system access, potentially allowing installation of additional persistent malicious software beyond the package itself.\n\nImmediate action is required: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. 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.

Indicators of compromise

Packages
  • @monitoring-lib/error-tracking

Remediation

  • Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the @monitoring-lib/error-tracking package from all affected systems
  • Perform a full security audit and malware scan of any system that had this package installed
  • Review system logs and network traffic for signs of unauthorized access or data exfiltration
  • Consider the affected systems as potentially fully compromised and plan for complete rebuild if critical infrastructure
  • Check npm audit logs and dependency trees to identify all projects using this package

Sources

  1. GitHub Advisory GHSA-5g45-cfrj-qc64 · GitHub Advisory Database

Cite this entry

"Malware in @monitoring-lib/error-tracking." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 15, 2026; last updated June 16, 2026. https://supplychainattack.org/incident/malware-in-monitoring-lib-error-tracking-1c6m49

Suggest a correction

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

  1. containedcritical

    Malware in flow-lending

    The npm package flow-lending was found to contain malware, resulting in full system compromise of any computer with the package installed or running. GitHub Security Advisory GHSA-pgcr-8w67-72j9 was published on 2026-06-16.

    npmCompromised package
  2. containedcritical

    Malware in flow-lending-sdk

    Malware was discovered in the npm package flow-lending-sdk. Systems with this package installed or running are considered fully compromised, with potential for complete system takeover.

    npmCompromised package
  3. containedcritical

    Malware in janus-flow

    Malware was discovered in the npm package janus-flow, 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.

    npmCompromised package
  4. containedcritical

    Malware in ttspc-server-sample

    The npm package ttspc-server-sample contains malware that grants full control of affected systems. Any computer with this package installed or running should be considered fully compromised.

    npmCompromised package