Which versions of express-bunker are malicious?

The following npm versions of express-bunker are flagged malicious: 6.1.0. Treat any of these as compromised.

How do I remediate express-bunker if I installed it?

express-bunker 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 express-bunker — how do I know if it already compromised me?

If express-bunker 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.

Is express-bunker part of a known attack campaign?

Yes — express-bunker is associated with the IN-MAL-2026-010324, GHSA-w7r5-8cmj-m893 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 express-bunker across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for express-bunker (version 6.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging express-bunker across your stack and pipelines.

Malicious package

express-bunkernpm

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

Malicious code in express-bunker (npm)

MAL-2026-10500

Immediate action

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

npm uninstall express-bunker

What this malware does

[email protected] ships a postinstall script that performs an HTTP GET to a hardcoded bare IP over plain HTTP (http://130.49.177.51:18080/p/dc-20260627-yandex-geobase) at npm install time, transmitting the package name, version, and a fixed campaign nonce (bb-express-bunker-20260628). The beacon fires unconditionally on every install with no opt-out. The package name and beacon path indicate a dependency-confusion squat against an internal namespace (yandex-geobase): any host or CI system that mis-resolves an internal dependency name to this public artifact silently signals successful name shadowing to the operator-controlled endpoint, disclosing installer environment information and confirming exploitability for follow-on attacks. A README self-label as a 'benign PoC' does not change the installer-side effect — the public artifact performs install-time outbound network I/O the installer did not opt into, and the same install vector could ship arbitrary code in a later version.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

6.1.0

Indicators of compromise (SHA-256)

68139b9a62e1d546de6ce2e46d5203782dbf54f1af2edbd2b8f509528eb0f000

27082ec28738f103f3d79213fcec51b4d66b71e422642ca9d530b3d005858f52

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for express-bunker (version 6.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging express-bunker across your stack and pipelines.
If you installed it — respond
express-bunker 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 express-bunker 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 express-bunker 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

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

Campaign

IN-MAL-2026-010324GHSA-w7r5-8cmj-m893

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks express-bunker-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