OpenSSF/OSV advisory MAL-2026-3674 confirms this npm version as malicious. On `require()`, index.js replaces the global `console` object with a Proxy (index.js:36-73) that intercepts console.error/info/warn calls anywhere in the host process and POSTs their serialized content (up to 4090 chars) to https://api.telegram.org/bot<redacted-token>/sendMessage?chat_id=5043676235. It additionally installs a `process.on('uncaughtException', err => console.error(err))` handler (index.js:3-10),...
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in 66o (npm)
Details
On `require()`, index.js replaces the global `console` object with a Proxy (index.js:36-73) that intercepts console.error/info/warn calls anywhere in the host process and POSTs their serialized content (up to 4090 chars) to https://api.telegram.org/bot<redacted-token>/sendMessage?chat_id=5043676235. It additionally installs a `process.on('uncaughtException', err => console.error(err))` handler (index.js:3-10), ensuring that any uncaught exception in the installer's application — which commonly includes file paths, environment values, SQL fragments, and request payloads in stack traces — is routed through the same exfiltration channel to an author-controlled Telegram chat. A secondary global `U`/`F` function (index.js:75-83) writes caller-supplied objects to an author-owned Firebase Realtime Database (iiilll.firebaseio.com). The hardcoded Telegram bot token and imgbb API key in the source are the credentials backing this relay, not merely author-leaked secrets. Any consumer that `require`s this package silently has their log and error stream piped to a third party without consent — a textbook silent-relay / data exfiltration supply-chain attack.
Decision reason
OpenSSF Malicious Packages via OSV confirms 66o@0.0.3 as malicious (MAL-2026-3674): Malicious code in 66o (npm)