Malicious code in hyper-kube-config (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4e6e8d8500ee41d92250882b57d98d805b381d2d08eeeac7bae55c3f5e417dff) package.json declares a preinstall hook that runs index.js on `npm install`. index.js collects the installer's hostname, username, home directory, DNS server configuration, current working directory, and the contents of /etc/passwd and /etc/hosts, then POSTs this payload over HTTPS to the hardcoded subdomain x75h3spwmlqq7bzriw6gm6w8azgq4hs6.oastify.com (a Burp Collaborator out-of-band interaction host). Execution is automatic at install time with no consent prompt and no documented purpose. The behavior matches a dependency-confusion reconnaissance beacon that exfiltrates installer host identity and local system files to an attacker-controlled endpoint. ## Source: ghsa-malware (a7d5d00e0c243819b3d1813314c4f4ef596f92a034d82e0a5acce92740bed5d5) 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 hyper-kube-config package (npm ecosystem) version 1.1.1 includes a preinstall hook declared in package.json that runs index.js during 'npm install'. The script collects various system identifiers and sensitive files, then sends this information to a hardcoded external domain (x75h3spwmlqq7bzriw6gm6w8azgq4hs6.oastify.com), which is a Burp Collaborator out-of-band interaction host. This automatic execution occurs without user consent or documented purpose, indicating malicious intent to perform reconnaissance and data exfiltration on the installer's system.
Potential Impact
Sensitive system information and local files are exfiltrated to an attacker-controlled endpoint during package installation. This compromises the confidentiality of the installer's environment and could facilitate further targeted attacks or reconnaissance. There is no indication of active exploitation in the wild at this time.
Mitigation Recommendations
No official patch or remediation guidance is provided. Users should avoid installing hyper-kube-config version 1.1.1. Verify package integrity and source before installation. Consider using trusted package registries and tools that detect malicious post-install scripts. Monitor for updates or advisories from the package maintainers or npm registry regarding this issue. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Malicious code in hyper-kube-config (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4e6e8d8500ee41d92250882b57d98d805b381d2d08eeeac7bae55c3f5e417dff) package.json declares a preinstall hook that runs index.js on `npm install`. index.js collects the installer's hostname, username, home directory, DNS server configuration, current working directory, and the contents of /etc/passwd and /etc/hosts, then POSTs this payload over HTTPS to the hardcoded subdomain x75h3spwmlqq7bzriw6gm6w8azgq4hs6.oastify.com (a Burp Collaborator out-of-band interaction host). Execution is automatic at install time with no consent prompt and no documented purpose. The behavior matches a dependency-confusion reconnaissance beacon that exfiltrates installer host identity and local system files to an attacker-controlled endpoint. ## Source: ghsa-malware (a7d5d00e0c243819b3d1813314c4f4ef596f92a034d82e0a5acce92740bed5d5) 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 hyper-kube-config package (npm ecosystem) version 1.1.1 includes a preinstall hook declared in package.json that runs index.js during 'npm install'. The script collects various system identifiers and sensitive files, then sends this information to a hardcoded external domain (x75h3spwmlqq7bzriw6gm6w8azgq4hs6.oastify.com), which is a Burp Collaborator out-of-band interaction host. This automatic execution occurs without user consent or documented purpose, indicating malicious intent to perform reconnaissance and data exfiltration on the installer's system.
Potential Impact
Sensitive system information and local files are exfiltrated to an attacker-controlled endpoint during package installation. This compromises the confidentiality of the installer's environment and could facilitate further targeted attacks or reconnaissance. There is no indication of active exploitation in the wild at this time.
Mitigation Recommendations
No official patch or remediation guidance is provided. Users should avoid installing hyper-kube-config version 1.1.1. Verify package integrity and source before installation. Consider using trusted package registries and tools that detect malicious post-install scripts. Monitor for updates or advisories from the package maintainers or npm registry regarding this issue. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-12392
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a735743bf8831d539159c59
Added to database: 08/05/2026, 15:31:15 UTC
Last enriched: 08/05/2026, 17:17:16 UTC
Last updated: 09/08/2026, 04:37:17 UTC
Views: 20
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.