Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in pino-utils

The npm package pino-utils was compromised and distributed with malware. Any system with the package installed should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with pino-utils installed
Ecosystems
Attack vectors
Affected entities
  • pino-utilsnpm package

The npm package pino-utils was found to contain malware. According to the GitHub advisory (GHSA-jwwm-v6rr-f5cv), any computer that has this package installed or running should be considered fully compromised.\n\nImmediate action is required: all secrets and keys stored on affected computers should be rotated immediately 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\nThe advisory was published on 2026-07-06 via the GitHub advisory database."

Indicators of compromise

Packages
  • pino-utils

Remediation

  • Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the pino-utils package from all affected systems
  • Audit system logs for unauthorized access or activity during the period the package was installed
  • Perform a full security assessment of any system that had pino-utils installed
  • Consider the affected system(s) potentially compromised and plan for full rebuild/replacement if critical infrastructure

Sources

  1. GitHub Advisory GHSA-jwwm-v6rr-f5cv · GitHub Advisory Database

Cite this entry

"Malware in pino-utils." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 6, 2026; last updated July 6, 2026. https://supplychainattack.org/incident/malware-in-pino-utils-10a8z7

Suggest a correction

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

  1. activecritical

    Malware in express-firegate

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

    npmCompromised package
  2. activecritical

    Malware in express-deflect

    Malware discovered in the npm package express-deflect. Systems with this package installed or running are considered fully compromised and require immediate remediation.

    npmCompromised package
  3. containedcritical

    Malware in chai-spycore

    Malware was discovered in the npm package chai-spycore, affecting any computer with the package installed or running. The compromise is considered critical as it grants full system control to an outside entity.

    npmCompromised package
  4. activecritical

    Malware in color-cli-log

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

    npmCompromised package