Malicious code in data-utils-d703 (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (e172168e5ac500d10ae42718a87676ad44a589b31dbeb5f902ea7fb1c4e6a984) The package declares a postinstall lifecycle hook ("postinstall": "node run.js" in package.json) that executes run.js automatically on install. run.js imports child_process, os, https, and http, calls os.hostname() and os.platform(), and contains multiple POST and GET HTTP request sites. This combination — automatic install-time execution plus host enumeration plus outbound HTTP — is the structural shape of an installer-side exfiltration or dropper, but the specific destinations, payload contents, and execution paths within run.js have not been fully traced, so attacker intent is not confirmed. Manual review of run.js is required to determine whether the network calls target attacker-controlled infrastructure and whether host data is exfiltrated or remote code is fetched and executed. ## Source: ghsa-malware (fee284139d8880599660922c960afc6566814acb8e76b0e23dab6cca599dd416) 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 data-utils-d703 npm package version 1.0.0 declares a postinstall lifecycle hook that automatically executes run.js during installation. The run.js script imports modules to gather host information (os.hostname(), os.platform()) and performs multiple HTTP POST and GET requests. This behavior is indicative of an installer-side exfiltration or dropper malware. Although the exact attacker intent and payload details have not been fully traced, the presence of automatic install-time execution combined with host enumeration and outbound network calls strongly suggests malicious activity. The package effectively compromises the host system, potentially allowing attackers to gain full control.
Potential Impact
Any system with data-utils-d703 version 1.0.0 installed should be considered fully compromised. Attackers may have exfiltrated sensitive host information or deployed additional malicious payloads. All secrets and keys stored on the affected system are at risk and must be rotated immediately from a secure environment. Simply removing the package does not guarantee removal of all malicious components or restoration of system integrity.
Mitigation Recommendations
Remove the data-utils-d703 package version 1.0.0 immediately from affected systems. Rotate all secrets, keys, and credentials that were stored or used on the compromised system from a separate, trusted environment. Conduct a thorough investigation for persistence mechanisms or additional malware installed as a result of this package. There is no official patch or fix available; remediation requires manual removal and secret rotation.
Malicious code in data-utils-d703 (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (e172168e5ac500d10ae42718a87676ad44a589b31dbeb5f902ea7fb1c4e6a984) The package declares a postinstall lifecycle hook ("postinstall": "node run.js" in package.json) that executes run.js automatically on install. run.js imports child_process, os, https, and http, calls os.hostname() and os.platform(), and contains multiple POST and GET HTTP request sites. This combination — automatic install-time execution plus host enumeration plus outbound HTTP — is the structural shape of an installer-side exfiltration or dropper, but the specific destinations, payload contents, and execution paths within run.js have not been fully traced, so attacker intent is not confirmed. Manual review of run.js is required to determine whether the network calls target attacker-controlled infrastructure and whether host data is exfiltrated or remote code is fetched and executed. ## Source: ghsa-malware (fee284139d8880599660922c960afc6566814acb8e76b0e23dab6cca599dd416) 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 data-utils-d703 npm package version 1.0.0 declares a postinstall lifecycle hook that automatically executes run.js during installation. The run.js script imports modules to gather host information (os.hostname(), os.platform()) and performs multiple HTTP POST and GET requests. This behavior is indicative of an installer-side exfiltration or dropper malware. Although the exact attacker intent and payload details have not been fully traced, the presence of automatic install-time execution combined with host enumeration and outbound network calls strongly suggests malicious activity. The package effectively compromises the host system, potentially allowing attackers to gain full control.
Potential Impact
Any system with data-utils-d703 version 1.0.0 installed should be considered fully compromised. Attackers may have exfiltrated sensitive host information or deployed additional malicious payloads. All secrets and keys stored on the affected system are at risk and must be rotated immediately from a secure environment. Simply removing the package does not guarantee removal of all malicious components or restoration of system integrity.
Mitigation Recommendations
Remove the data-utils-d703 package version 1.0.0 immediately from affected systems. Rotate all secrets, keys, and credentials that were stored or used on the compromised system from a separate, trusted environment. Conduct a thorough investigation for persistence mechanisms or additional malware installed as a result of this package. There is no official patch or fix available; remediation requires manual removal and secret rotation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6112
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-655h-34jr-cj9x"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50ba5c68715ace4357efe2
Added to database: 07/10/2026, 09:24:44 UTC
Last enriched: 07/10/2026, 09:44:57 UTC
Last updated: 07/19/2026, 07:35:16 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.