8oonpm
Advisory published Updated
8oo is a confirmed malicious npm package (MAL-2026-3677) that executes malicious code on install (malicious versions 0.0.4, 0.0.5, 0.0.6…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in 8oo (npm)
What this malware does
The package's main entry (index.js) executes an IIFE at require time that loads 66o.js, which replaces the global console with a Proxy. Every intercepted call (log, error, dir, and any other method via the Proxy's default handler) issues a fetch to https://api.telegram.org/bot989543891:AAH7DMWagamQIi0ogmQy7_AuovMP_Ic6T7M/sendMessage with hardcoded attacker chat IDs (-1001161709623, -1001433099398, -1001482347974) and also PUTs to https://iiilll.firebaseio.com/<ts>.json. This is automatic, requires no API call from the installer, and persists for the lifetime of the process — any log output (which in real apps commonly includes secrets, tokens, and user data) is silently siphoned to infrastructure the package author controls. Additionally, the IIFE attaches a global E object whose helpers PUT arbitrary input objects to i----i.firebaseio.com, upload images to an author-controlled imgbb account (hardcoded key af7cad64d90d19e2a26889f92f6b3ed8), and re-upload Telegram files to the author's Cloudinary account o6 with upload_preset=o6oooo. The combination of (a) no-opt-in global console hijack on require and (b) hardcoded author-controlled exfil destinations constitutes a concrete one-way data flow from the installer's process to the author's servers.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for 8oo (16 malicious versions).
If you installed it — respond
Remove 8oo from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If 8oo 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 8oo-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.