Malware in pino-debugging
Malware was discovered in the npm package pino-debugging. Systems with this package installed or running are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with pino-debugging installed or running
- Ecosystems
- Attack vectors
- Affected entities
- pino-debuggingnpm package
A critical malware incident was identified in the npm package pino-debugging. According to the GitHub Advisory (GHSA-jwq5-g2xm-r48w), any computer with 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 system. While the malicious 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, as the attacker may have gained full control of the system.\n\nThis represents a supply chain attack through a compromised npm package with potential for widespread impact across all systems that have installed or executed this dependency.
Indicators of compromise
- Packages
- pino-debugging
Remediation
- Immediately isolate any system with pino-debugging installed from the network
- Rotate all secrets, API keys, and credentials from a clean, uncompromised system
- Remove the pino-debugging package from all affected systems
- Conduct a full forensic investigation of affected systems for additional malware or persistence mechanisms
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if compromise is confirmed
- Audit all systems that may have been accessed using credentials stored on compromised machines
Sources
- GitHub Advisory GHSA-jwq5-g2xm-r48w · GitHub Advisory Database
Cite this entry
"Malware in pino-debugging." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 20, 2026; last updated August 20, 2026. https://supplychainattack.org/incident/malware-in-pino-debugging-1alhi6
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in rust-testing-utils (npm)
The npm package rust-testing-utils contained malicious code that impersonates the pino logger and executes remotely-fetched code with arbitrary privileges. The package spawns a child process that decodes a hardcoded URL, fetches attacker-controlled content, and executes it via Function constructor with full module-loading capability.
npmCompromised packageMalicious commit - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malware in hydration-dim-kit
Malware was discovered in the npm package hydration-dim-kit. 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