badbunny@0.0.0-stage
Malicious code in badbunny (npm)
Analysis
badbunny@0.0.0-stage contains no executable code: the tarball is two files (330 bytes unpacked) — a package.json marked "stub": true with the description "Temporary package placeholder for staged publishing" and no scripts, bin entries, dependencies or lifecycle hooks, plus a README stating the version is a temporary placeholder for a package that is "awaiting a staged release". Nothing in this version runs on install or require, and no network, exec, or credential-access code is present. The version functions as a name reservation / staging placeholder, consistent with preparing a package for a later, operational release; the analysis of this version is metadata-only and no payload artifacts exist in it. The package name relates to the Bun runtime hijacking technique ("badbunny"), and the npm account also publishes x3r0day-bunnyhijack-poc.
- analyzed by
- Leitwacht
- first seen
- Nov 10, 2026, 02:21 PM
- analyzed
- Nov 10, 2026, 02:22 PM
Related advisories
- sauruspro-bail@5.3.1
- @charape/baileys@1.0.7
- @trashcore/baileys@4.2.2
- @trashcore/baileys@4.1.8
- @trashcore/baileys@4.1.5
- @trashcore/baileys@4.1.3
- @langitdeveloper/baileys@2.1.9
- @trashcore/baileys@4.1.7
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.