Malicious code in elephant-tusk-runner (npm)
The elephant-tusk-runner npm package versions 1.0.0 and 1.0.1 contain malicious code that starts an Express and WebSocket server bound to all network interfaces with open CORS and no authentication. This server exposes endpoints that allow remote attackers to spawn interactive shells and execute arbitrary commands on the host machine. The exposed functionality includes spawning bash or PowerShell shells, executing commands like git clone, npm install, PHP artisan commands, and killing arbitrary processes. This creates a severe remote code execution and remote shell access risk on any machine running the tool, especially on shared or reachable networks.
AI Analysis
Technical Summary
The elephant-tusk-runner npm package (versions 1.0.0 and 1.0.1) contains embedded malicious code that launches an unauthenticated Express and WebSocket server listening on port 4201 bound to 0.0.0.0, allowing any network peer to access it. The server has fully open CORS and no authentication, exposing endpoints that spawn PTY shells (bash or PowerShell) and pipe network input directly to these shells, enabling interactive remote shell access. Additional endpoints allow execution of arbitrary commands including git clone with attacker-controlled URLs, PHP artisan commands, npm install, execution of arbitrary PHP files, and process termination commands. This results in a full remote code execution surface on any developer or build machine running the package.
Potential Impact
This malicious package enables unauthenticated remote attackers to gain interactive shell access and execute arbitrary commands on the host system. This can lead to complete system compromise, data theft, destruction, or lateral movement within a network. The risk is especially high on shared or network-reachable developer or build machines where the package is installed and running.
Mitigation Recommendations
No official patch or fix is currently documented. Users should immediately uninstall the elephant-tusk-runner package versions 1.0.0 and 1.0.1 and avoid running it on any system. Network access to port 4201 should be blocked if the package must be used temporarily. Monitor systems for signs of compromise and consider rebuilding affected hosts. Check vendor or repository advisories for updates or remediation guidance.
Malicious code in elephant-tusk-runner (npm)
Description
The elephant-tusk-runner npm package versions 1.0.0 and 1.0.1 contain malicious code that starts an Express and WebSocket server bound to all network interfaces with open CORS and no authentication. This server exposes endpoints that allow remote attackers to spawn interactive shells and execute arbitrary commands on the host machine. The exposed functionality includes spawning bash or PowerShell shells, executing commands like git clone, npm install, PHP artisan commands, and killing arbitrary processes. This creates a severe remote code execution and remote shell access risk on any machine running the tool, especially on shared or reachable networks.
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 elephant-tusk-runner npm package (versions 1.0.0 and 1.0.1) contains embedded malicious code that launches an unauthenticated Express and WebSocket server listening on port 4201 bound to 0.0.0.0, allowing any network peer to access it. The server has fully open CORS and no authentication, exposing endpoints that spawn PTY shells (bash or PowerShell) and pipe network input directly to these shells, enabling interactive remote shell access. Additional endpoints allow execution of arbitrary commands including git clone with attacker-controlled URLs, PHP artisan commands, npm install, execution of arbitrary PHP files, and process termination commands. This results in a full remote code execution surface on any developer or build machine running the package.
Potential Impact
This malicious package enables unauthenticated remote attackers to gain interactive shell access and execute arbitrary commands on the host system. This can lead to complete system compromise, data theft, destruction, or lateral movement within a network. The risk is especially high on shared or network-reachable developer or build machines where the package is installed and running.
Mitigation Recommendations
No official patch or fix is currently documented. Users should immediately uninstall the elephant-tusk-runner package versions 1.0.0 and 1.0.1 and avoid running it on any system. Network access to port 4201 should be blocked if the package must be used temporarily. Monitor systems for signs of compromise and consider rebuilding affected hosts. Check vendor or repository advisories for updates or remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13445
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a7573b6bf8831d539d93bf7
Added to database: 08/07/2026, 05:57:10 UTC
Last enriched: 08/07/2026, 07:32:22 UTC
Last updated: 09/21/2026, 23:42:11 UTC
Views: 25
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.