Malicious code in set-proto-chain (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (bdb11eef3afbfc268bd48a18737884246861c7ae9e6a3d29901ae1379216c633) lib/index.js contains a base64-encoded URL (decoding to https://jsonkeeper.com/b/BN77K, an anonymous mutable paste host) that is fetched via axios.get; the response's `.data.cookie` field is then written to the stdin of a detached `node` child process for execution. The top-level index.js calls getThetaInterface() unconditionally, and package.json declares `postinstall: node index.js`, so the fetch-and-execute path fires automatically on `npm install` as well as on require(). The fetched payload is attacker-controlled and can change at any time. The package additionally impersonates the legitimate `proto-chain` package (README header `# proto-chain`, runtime error messages referencing `require('proto-chain')`), making accidental installs more likely. ## Source: ghsa-malware (e5464b83f14b49df255a13a51392d93c6632bd5605d85a3c670d99d37b967417) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
The 'set-proto-chain' npm package (version 1.0.3) includes a malicious script in its index.js that decodes a base64 URL pointing to an anonymous mutable paste host. This URL is fetched via axios.get, and the response's 'data.cookie' field is executed by writing it to the stdin of a detached node child process. The execution path triggers automatically on 'npm install' due to a postinstall script and also on require(). The package impersonates the legitimate 'proto-chain' package to deceive users. Because the fetched payload is attacker-controlled and can change at any time, any system with this package installed is at high risk of full compromise.
Potential Impact
Any computer with 'set-proto-chain' version 1.0.3 installed or running is considered fully compromised. The attacker gains remote code execution capabilities, potentially leading to complete system takeover. All secrets and keys stored on the compromised system are at risk and should be rotated immediately. Removing the package alone does not guarantee removal of all malicious artifacts or backdoors introduced by the attacker.
Mitigation Recommendations
There is no official patch or fix available for this malicious package. Immediate removal of 'set-proto-chain' version 1.0.3 from all systems is strongly recommended. All secrets, credentials, and keys stored on affected systems should be rotated from a secure, uncompromised environment. Consider rebuilding or thoroughly cleaning affected systems due to the high likelihood of persistent compromise. Avoid installing packages that impersonate legitimate ones and verify package authenticity before installation.
Malicious code in set-proto-chain (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (bdb11eef3afbfc268bd48a18737884246861c7ae9e6a3d29901ae1379216c633) lib/index.js contains a base64-encoded URL (decoding to https://jsonkeeper.com/b/BN77K, an anonymous mutable paste host) that is fetched via axios.get; the response's `.data.cookie` field is then written to the stdin of a detached `node` child process for execution. The top-level index.js calls getThetaInterface() unconditionally, and package.json declares `postinstall: node index.js`, so the fetch-and-execute path fires automatically on `npm install` as well as on require(). The fetched payload is attacker-controlled and can change at any time. The package additionally impersonates the legitimate `proto-chain` package (README header `# proto-chain`, runtime error messages referencing `require('proto-chain')`), making accidental installs more likely. ## Source: ghsa-malware (e5464b83f14b49df255a13a51392d93c6632bd5605d85a3c670d99d37b967417) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
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 'set-proto-chain' npm package (version 1.0.3) includes a malicious script in its index.js that decodes a base64 URL pointing to an anonymous mutable paste host. This URL is fetched via axios.get, and the response's 'data.cookie' field is executed by writing it to the stdin of a detached node child process. The execution path triggers automatically on 'npm install' due to a postinstall script and also on require(). The package impersonates the legitimate 'proto-chain' package to deceive users. Because the fetched payload is attacker-controlled and can change at any time, any system with this package installed is at high risk of full compromise.
Potential Impact
Any computer with 'set-proto-chain' version 1.0.3 installed or running is considered fully compromised. The attacker gains remote code execution capabilities, potentially leading to complete system takeover. All secrets and keys stored on the compromised system are at risk and should be rotated immediately. Removing the package alone does not guarantee removal of all malicious artifacts or backdoors introduced by the attacker.
Mitigation Recommendations
There is no official patch or fix available for this malicious package. Immediate removal of 'set-proto-chain' version 1.0.3 from all systems is strongly recommended. All secrets, credentials, and keys stored on affected systems should be rotated from a secure, uncompromised environment. Consider rebuilding or thoroughly cleaning affected systems due to the high likelihood of persistent compromise. Avoid installing packages that impersonate legitimate ones and verify package authenticity before installation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6079
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-7p39-r7q7-jcv7"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a4c341227e9c797195f7c7a
Added to database: 07/06/2026, 23:02:42 UTC
Last enriched: 07/07/2026, 00:37:00 UTC
Last updated: 07/18/2026, 17:27:21 UTC
Views: 5
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.