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

com.epi.e2e_testnpm

com.epi.e2e_test is a confirmed malicious npm package (MAL-2026-17415) that opens a backdoor for remote access (malicious version 1.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in com.epi.e2e_test (npm)

MAL-2026-17415
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall com.epi.e2e_test

What this malware does

package.json declares a preinstall script that runs index.js on npm install. index.js collects host identifiers (os.homedir(), os.hostname(), os.userInfo().username, dns.getServers(), current working directory) along with the contents of the package.json and POSTs them over HTTPS to the hardcoded external host meta.brs.cx. This behavior fires automatically on install with no user interaction, and the collected data is characteristic of dependency-confusion / internal-name reconnaissance beacons used to identify targets for follow-on attacks.

Malicious versions

1 flagged
1.2.2

Indicators of compromise (SHA-256)

5a0c1068af335818f2b9d905f2d39ebe594f84a6c63e470877692554bc95103b

Detection & response playbook

Backdoor / remote access

  1. Find it

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

  2. If you installed it — respond

    com.epi.e2e_test 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.

  3. Did it already run?

    If com.epi.e2e_test 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 com.epi.e2e_test 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. com.epi.e2e_test on npm has been identified as a malicious package (version 1.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020822

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks com.epi.e2e_test-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
com.epi.e2e_test (npm) malicious package — MAL-2026-17415 | O3 Security