bug-monoreponpm
Malicious code in bug-monorepo (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
package.json declares preinstall: node index.js, causing index.js to run automatically on npm install. The script collects hostname, username, home directory, DNS servers, and the full package.json, and reads /etc/passwd and /etc/hosts (index.js:18), then HTTPS-POSTs the JSON payload to cp5uzinglyy3ifb8gvvgvq5qvh19p0dp.oastify.com (a Burp Collaborator out-of-band subdomain controlled by the attacker). Empty author/description fields and the generic bug-monorepo name are consistent with a dependency-confusion recon package targeting an internal namespace. Installing this package leaks host identity and sensitive system file contents to an attacker-controlled endpoint.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bug-monorepo (version 3.1.94). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bug-monorepo across your stack and pipelines.
If you installed it — respond
Remove bug-monorepo 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 bug-monorepo was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks bug-monorepo before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks bug-monorepo-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.