Malicious code in @sidp-kiosk/test-npm-snurkeburk-hackerone (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (69a832d2eb4042899a17a745bac70590844ba320f3e181580314687c664e5159) The package's package.json declares a preinstall script that runs index.js automatically on `npm install`. index.js shells out via child_process.exec to collect the installer's hostname, current working directory, username, a package marker, and the machine's public IP (fetched via curl to ifconfig.me). The aggregated output is hex-encoded with xxd and split into DNS labels queried via nslookup against subdomains of snurkeburk.com, a DNS-tunnel exfiltration channel that bypasses egress HTTP filtering. Installing this package causes host identifiers and public IP to leave the machine to an attacker-controlled DNS namespace.
AI Analysis
Technical Summary
This threat involves a malicious npm package that declares a preinstall script in its package.json. The script executes index.js on installation, which uses child_process.exec to gather sensitive host information including hostname, current working directory, username, a package marker, and the public IP address (retrieved via curl to ifconfig.me). The collected data is hex-encoded and exfiltrated through DNS queries to subdomains of snurkeburk.com, effectively creating a DNS tunnel that circumvents typical HTTP egress filtering controls. This behavior results in unauthorized data leakage to an attacker-controlled DNS namespace.
Potential Impact
Installation of the affected package versions results in unauthorized exfiltration of host identifiers and the public IP address to an attacker-controlled DNS domain. This can lead to privacy breaches and potential reconnaissance for further attacks. The exfiltration method bypasses HTTP filtering by using DNS tunneling, making detection and blocking more challenging.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix or official guidance is available, avoid installing or using the affected package versions (=1.999.0 and =2.999.0). Monitor package sources carefully and consider using package integrity verification or trusted registries to prevent installation of malicious packages.
Malicious code in @sidp-kiosk/test-npm-snurkeburk-hackerone (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (69a832d2eb4042899a17a745bac70590844ba320f3e181580314687c664e5159) The package's package.json declares a preinstall script that runs index.js automatically on `npm install`. index.js shells out via child_process.exec to collect the installer's hostname, current working directory, username, a package marker, and the machine's public IP (fetched via curl to ifconfig.me). The aggregated output is hex-encoded with xxd and split into DNS labels queried via nslookup against subdomains of snurkeburk.com, a DNS-tunnel exfiltration channel that bypasses egress HTTP filtering. Installing this package causes host identifiers and public IP to leave the machine to an attacker-controlled DNS namespace.
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
This threat involves a malicious npm package that declares a preinstall script in its package.json. The script executes index.js on installation, which uses child_process.exec to gather sensitive host information including hostname, current working directory, username, a package marker, and the public IP address (retrieved via curl to ifconfig.me). The collected data is hex-encoded and exfiltrated through DNS queries to subdomains of snurkeburk.com, effectively creating a DNS tunnel that circumvents typical HTTP egress filtering controls. This behavior results in unauthorized data leakage to an attacker-controlled DNS namespace.
Potential Impact
Installation of the affected package versions results in unauthorized exfiltration of host identifiers and the public IP address to an attacker-controlled DNS domain. This can lead to privacy breaches and potential reconnaissance for further attacks. The exfiltration method bypasses HTTP filtering by using DNS tunneling, making detection and blocking more challenging.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix or official guidance is available, avoid installing or using the affected package versions (=1.999.0 and =2.999.0). Monitor package sources carefully and consider using package integrity verification or trusted registries to prevent installation of malicious packages.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-14161
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a84fa65c6e8be0332ef130f
Added to database: 08/19/2026, 00:35:49 UTC
Last enriched: 08/19/2026, 00:50:27 UTC
Last updated: 10/02/2026, 16:02:35 UTC
Views: 191
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.