MAL-2026-6583: Malicious code in pino-debugging (npm)
The pino-debugging npm package impersonates the legitimate pino-debug package and contains malicious code. When imported or required, it loads a dependency chain that contacts a hardcoded command-and-control server at fundraiser-success.vercel.app and executes a payload within the consumer's Node.js process. The package also modifies Node's module loading mechanism to silently intercept require calls for the popular debug package, extending its malicious influence across the dependency tree. The package's own documentation openly describes this supply-chain attack chain, while misleadingly claiming zero vulnerabilities and production readiness.
AI Analysis
Technical Summary
The pino-debugging npm package (versions 1.1.3 and 1.1.4) is a malicious package impersonating the legitimate pino-debug. Its main entry point requires a transitive dependency 'loadutils' that further depends on code contacting a hardcoded C2 server at https://fundraiser-success.vercel.app. This server delivers a payload executed in the consumer's Node.js process. Additionally, pino-debugging mutates Node's require('module').wrap function to rewrite require calls inside any node_modules/debug module, effectively routing consumers of the widely used debug package through its malicious shim. The shipped files openly describe this attack chain, including payload execution and screenshot capture, while the README and SECURITY files falsely assert the package is production ready and free of vulnerabilities.
Potential Impact
Consumers of the pino-debugging package versions 1.1.3 and 1.1.4 risk executing arbitrary malicious code delivered from a remote command-and-control server within their Node.js environment. This includes potential unauthorized actions such as screenshot capture. The package's modification of the module loading system allows it to silently affect other dependencies that use the debug package, increasing the attack surface and potential impact across the dependency tree.
Mitigation Recommendations
No official patch or remediation is currently documented for this malicious package. Users should immediately remove pino-debugging versions 1.1.3 and 1.1.4 from their projects and dependency trees. Avoid installing or using this package. Verify dependencies to ensure no transitive inclusion of pino-debugging. Monitor for any suspicious network connections to fundraiser-success.vercel.app and audit Node.js processes for unauthorized code execution. Patch status is not yet confirmed — check vendor advisories or trusted sources for updates.
MAL-2026-6583: Malicious code in pino-debugging (npm)
Description
The pino-debugging npm package impersonates the legitimate pino-debug package and contains malicious code. When imported or required, it loads a dependency chain that contacts a hardcoded command-and-control server at fundraiser-success.vercel.app and executes a payload within the consumer's Node.js process. The package also modifies Node's module loading mechanism to silently intercept require calls for the popular debug package, extending its malicious influence across the dependency tree. The package's own documentation openly describes this supply-chain attack chain, while misleadingly claiming zero vulnerabilities and production readiness.
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 npm package (versions 1.1.3 and 1.1.4) is a malicious package impersonating the legitimate pino-debug. Its main entry point requires a transitive dependency 'loadutils' that further depends on code contacting a hardcoded C2 server at https://fundraiser-success.vercel.app. This server delivers a payload executed in the consumer's Node.js process. Additionally, pino-debugging mutates Node's require('module').wrap function to rewrite require calls inside any node_modules/debug module, effectively routing consumers of the widely used debug package through its malicious shim. The shipped files openly describe this attack chain, including payload execution and screenshot capture, while the README and SECURITY files falsely assert the package is production ready and free of vulnerabilities.
Potential Impact
Consumers of the pino-debugging package versions 1.1.3 and 1.1.4 risk executing arbitrary malicious code delivered from a remote command-and-control server within their Node.js environment. This includes potential unauthorized actions such as screenshot capture. The package's modification of the module loading system allows it to silently affect other dependencies that use the debug package, increasing the attack surface and potential impact across the dependency tree.
Mitigation Recommendations
No official patch or remediation is currently documented for this malicious package. Users should immediately remove pino-debugging versions 1.1.3 and 1.1.4 from their projects and dependency trees. Avoid installing or using this package. Verify dependencies to ensure no transitive inclusion of pino-debugging. Monitor for any suspicious network connections to fundraiser-success.vercel.app and audit Node.js processes for unauthorized code execution. Patch status is not yet confirmed — check vendor advisories or trusted sources for updates.
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: 06/29/2026, 22:35:48 UTC
Last updated: 06/30/2026, 00:49:02 UTC
Views: 4
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.