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

e2e-test-utilsnpm

e2e-test-utils is a confirmed malicious npm package (MAL-2025-47990) that executes malicious code on install (malicious version 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in e2e-test-utils (npm)

MAL-2025-47990
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall e2e-test-utils

What this malware does

The package communicates with a domain associated with malicious activity.

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
2.0.0

Indicators of compromise (SHA-256)

c9c8d68688f22fea09a5713fa230e86e17ec757b0ab4f80311cbc5312fd0cbf0
406c86f342d684efae752ade68ecfc6feda83248ea85c1f7e5e0d6ee8cd2f93b
d3248055ae0920a709c6b2a17305f2a884053a19bfdb0658012bddcf0e52b0f1

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 e2e-test-utils (version 2.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging e2e-test-utils across your stack and pipelines.

  2. If you installed it — respond

    Remove e2e-test-utils 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 e2e-test-utils 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 e2e-test-utils 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. e2e-test-utils on npm has been identified as a malicious package (version 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cjp6-4vw5-fw77RLMA-2025-05347RLUA-2025-05773

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks e2e-test-utils-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

e2e-test-utils (npm) malicious package — MAL-2025-47990 | O3 Security