Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

z-shop-js-envnpm

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

MAL-2026-727
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall z-shop-js-env

What this malware does

The package z-shop-js-env 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

2 flagged
0.0.1-security56.2.1

Indicators of compromise (SHA-256)

9a1ecf70acc2b9592534b8c85342bac4b887b74656f5c9d971d51375fed00d9f
c910274a4f0635a1545efdbfbd102ee02489acc2cc2e37c2c5bec67beb6ea1eb
0004bd95fa013ec39f8ffaf0c3d0193c44d21832e3650d829f47dbcbab82dca3

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for z-shop-js-env (2 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-js-env across your stack and pipelines.

  2. If you installed it — respond

    Remove z-shop-js-env 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.

  3. Did it already run?

    If z-shop-js-env 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.

  4. How O3 protects you

    O3 blocks z-shop-js-env 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-js-env on npm has been identified as a malicious package (versions 0.0.1-security, 56.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6hph-mcq5-c6c3RLMA-2026-01667

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks z-shop-js-env-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.

z-shop-js-env (npm) malicious package — MAL-2026-727 | O3 Security