Which versions of z-shop-event-bus are malicious?

The following npm versions of z-shop-event-bus are flagged malicious: 0.0.1-security, 1.0.0, 56.2.1. Treat any of these as compromised.

How do I remediate z-shop-event-bus if I installed it?

Remove z-shop-event-bus 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.

I already installed z-shop-event-bus — how do I know if it already compromised me?

If z-shop-event-bus 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 z-shop-event-bus part of a known attack campaign?

Yes — z-shop-event-bus is associated with the GHSA-xfv7-mr73-872w, RLMA-2026-01666 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 z-shop-event-bus 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 z-shop-event-bus (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging z-shop-event-bus across your stack and pipelines.

Malicious package

z-shop-event-busnpm

Malicious code in z-shop-event-bus (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-726

Immediate action

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

npm uninstall z-shop-event-bus

What this malware does

The package z-shop-event-bus was found to contain malicious code.

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

3 flagged

0.0.1-security1.0.056.2.1

Indicators of compromise (SHA-256)

4e51cf3a7018daddc8f2ba956f6e030ec57f8bad1e45102d29243c9dd13d48fa

db54dce43d20da63e308cbd0ae4785225d093b5bd8b5d7c202e0f17a19ba11c2

d7bdaf8bd79608b2638976b944e842b4786270e1cc5e6ef85f34c4479f067776

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for z-shop-event-bus (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging z-shop-event-bus across your stack and pipelines.
If you installed it — respond
Remove z-shop-event-bus 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 z-shop-event-bus 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 z-shop-event-bus 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. z-shop-event-bus on npm has been identified as a malicious package (versions 0.0.1-security, 1.0.0, 56.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xfv7-mr73-872wRLMA-2026-01666

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks z-shop-event-bus-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.

Malware detection Runtime egress monitoring