Malicious code in pino-debugging (npm)
The pino-debugging npm package is a malicious typosquat of the legitimate pino-debug package. It contains a backdoor that automatically runs attacker-controlled code when preloaded, connecting to a hardcoded command and control (C2) server to receive and execute payloads. The package uses obfuscated dependency renaming to evade detection. Versions 1.1.3 and 1.1.4 are affected. This is a supply chain attack vector that can compromise the security of systems that install and preload this package.
AI Analysis
Technical Summary
The pino-debugging package is a malicious typosquatting package targeting users of the legitimate pino-debug npm package. It ships with an index.js that requires a dependency named 'loadutils' and invokes it on preload, causing the attacker's code to run automatically. The package contains a backdoor that connects to https://fundraiser-success.vercel.app to receive and execute remote payloads, controlled via environment variables DEBUG_C2_SERVER, DEBUG_C2_PROTOCOL, and DEBUG_VERBOSE. The dependency was renamed from previously documented malicious chains to evade name-based detection. Installing and preloading pino-debugging versions 1.1.3 and 1.1.4 results in execution of attacker-controlled code and beaconing to a hardcoded C2 server, representing a critical supply chain compromise.
Potential Impact
Systems that install and preload pino-debugging versions 1.1.3 or 1.1.4 will execute attacker-controlled code automatically, potentially allowing remote code execution and persistent backdoor access. This compromises the integrity and confidentiality of affected systems and can lead to further malicious activity controlled by the attacker.
Mitigation Recommendations
Avoid installing or preloading the pino-debugging package, especially versions 1.1.3 and 1.1.4. Since this is a malicious typosquat package, replace any usage with the legitimate pino-debug package. There is no official patch or fix for pino-debugging as it is a malicious package; remediation involves removing it from dependencies and lockfiles. Monitor dependency trees for typosquat or suspicious packages to prevent supply chain attacks.
Malicious code in pino-debugging (npm)
Description
The pino-debugging npm package is a malicious typosquat of the legitimate pino-debug package. It contains a backdoor that automatically runs attacker-controlled code when preloaded, connecting to a hardcoded command and control (C2) server to receive and execute payloads. The package uses obfuscated dependency renaming to evade detection. Versions 1.1.3 and 1.1.4 are affected. This is a supply chain attack vector that can compromise the security of systems that install and preload this package.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The pino-debugging package is a malicious typosquatting package targeting users of the legitimate pino-debug npm package. It ships with an index.js that requires a dependency named 'loadutils' and invokes it on preload, causing the attacker's code to run automatically. The package contains a backdoor that connects to https://fundraiser-success.vercel.app to receive and execute remote payloads, controlled via environment variables DEBUG_C2_SERVER, DEBUG_C2_PROTOCOL, and DEBUG_VERBOSE. The dependency was renamed from previously documented malicious chains to evade name-based detection. Installing and preloading pino-debugging versions 1.1.3 and 1.1.4 results in execution of attacker-controlled code and beaconing to a hardcoded C2 server, representing a critical supply chain compromise.
Potential Impact
Systems that install and preload pino-debugging versions 1.1.3 or 1.1.4 will execute attacker-controlled code automatically, potentially allowing remote code execution and persistent backdoor access. This compromises the integrity and confidentiality of affected systems and can lead to further malicious activity controlled by the attacker.
Mitigation Recommendations
Avoid installing or preloading the pino-debugging package, especially versions 1.1.3 and 1.1.4. Since this is a malicious typosquat package, replace any usage with the legitimate pino-debug package. There is no official patch or fix for pino-debugging as it is a malicious package; remediation involves removing it from dependencies and lockfiles. Monitor dependency trees for typosquat or suspicious packages to prevent supply chain attacks.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6583
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a42ed6927e9c79719938292
Added to database: 06/29/2026, 22:10:49 UTC
Last enriched: 07/10/2026, 13:04:36 UTC
Last updated: 07/30/2026, 15:56:33 UTC
Views: 39
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.