Which versions of bugexploit are malicious?

The following npm versions of bugexploit are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate bugexploit if I installed it?

bugexploit establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed bugexploit — how do I know if it already compromised me?

If bugexploit 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.

Is bugexploit part of a known attack campaign?

Yes — bugexploit is associated with the IN-MAL-2026-009753 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find bugexploit across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bugexploit (version 99.9.9).

Malicious package

bugexploitnpm

Advisory published Jul 12, 2026Updated Jul 12, 2026

bugexploit is a confirmed malicious npm package (MAL-2026-10201) that opens a backdoor for remote access (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bugexploit (npm)

MAL-2026-10201

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall bugexploit

What this malware does

package.json declares a postinstall script that runs node index.js. On npm install, index.js collects the installer's username (os.userInfo()), hostname (os.hostname()), and current working directory (process.cwd()), then POSTs them as JSON via https.request to the hardcoded endpoint https://webhook.site/cd23dfb8-a0fc-4ff7-818c-f7812fcb4bec. The transmission is unconditional and fires automatically on default install. The destination is a generic webhook-capture service unrelated to any declared package purpose, and the collected fields are host identifiers useful for victim triage / beacon confirmation.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

745f81b0c53fa121939d4f71680783860795a394eb30308f6e7e2dcf29401c92

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for bugexploit (version 99.9.9).
If you installed it — respond
bugexploit establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If bugexploit 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

No. bugexploit on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009753

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bugexploit-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database