MAL-2026-3674 Malicious code in 66o (npm)
Malicious package
Published
MAL-2026-3674 is a malicious package: 66o (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-3674/ (Markdown: https://insights.sbomify.com/MAL-2026-3674/index.md)
- Package
- 66o
- Registry
- npm
What is MAL-2026-3674?
MAL-2026-3674 is a malicious package in 66o, published on 12 May 2026.
Official description
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 requires 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.What should I do about MAL-2026-3674?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.