red-bull-venue-toolsnpm
Advisory published Updated
red-bull-venue-tools is a confirmed malicious npm package (MAL-2025-5455) that typosquats a legitimate package to trick installs (malicious version 19.2.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in red-bull-venue-tools (npm)
What this malware does
The package communicates with a domain associated with malicious activity.
package.json declares preinstall=node index.js, which fires automatically on npm install. index.js collects host reconnaissance — os.hostname(), os.platform()/arch, os.homedir(), os.userInfo() (username/uid/gid/shell), whoami and id shell command output via child_process.exec, OS info, and cwd — and POSTs the JSON payload to a hardcoded Burp Collaborator OAST subdomain at https://theyfiesr9w2p5moyrr9yn6lscy3mvak.oastify.com/detox56. The package name impersonates a Red Bull brand namespace, consistent with a targeted reconnaissance / dependency-confusion probe against an internal Red Bull build environment. Installer harm is concrete: every npm install of this version leaks installer identity and host fingerprint to an attacker-controlled out-of-band destination.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for red-bull-venue-tools (version 19.2.1).
If you installed it — respond
red-bull-venue-tools is a typosquat — you almost certainly intended a legitimately-named package. Remove red-bull-venue-tools, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If red-bull-venue-tools was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks red-bull-venue-tools-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.