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

epm-service-module-v2npm

epm-service-module-v2 is a confirmed malicious npm package (MAL-2026-5851) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in epm-service-module-v2 (npm)

MAL-2026-5851
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall epm-service-module-v2

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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

4 flagged
1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

f7b0de1b676618a68f5707692c33cef713882df9ef3ecdb5c73391837669af7b
8fd918cea189b1bc56c3747261e190b331708c8dc3e799d144e95c33c0ebe3c0
d6e121163b02dca047d606582f79a205a426112e4f6801c90fc3254c04954212
80cbdcdfd5eef2d5d640b2a3bee1d20b664c27d299f595c6b382b6d1cdbff2d7
b08516985e24b0f92e531519cb22a68a0e1e14faa07c0f597d992834360b84d7

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 epm-service-module-v2 (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging epm-service-module-v2 across your stack and pipelines.

  2. If you installed it — respond

    Remove epm-service-module-v2 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 epm-service-module-v2 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 epm-service-module-v2 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. epm-service-module-v2 on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-633w-wc3j-7jrfIN-MAL-2026-008877IN-MAL-2026-008878IN-MAL-2026-008910IN-MAL-2026-009543

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks epm-service-module-v2-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.

Explore

epm-service-module-v2 (npm) malicious package — MAL-2026-5851 | O3 Security