Which versions of eb-csr are malicious?

The following npm versions of eb-csr are flagged malicious: 1.0.0, 9.1.143. Treat any of these as compromised.

How do I remediate eb-csr if I installed it?

Remove eb-csr 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 eb-csr — how do I know if it already compromised me?

If eb-csr was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is eb-csr part of a known attack campaign?

Yes — eb-csr is associated with the GHSA-x757-3w6f-f9rm, RLMA-2026-01268 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 eb-csr across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for eb-csr (2 malicious versions).

Malicious package

eb-csrnpm

Advisory published Dec 30, 2025Updated Mar 19, 2026

eb-csr is a confirmed malicious npm package (MAL-2025-192967) that executes malicious code on install (malicious versions 1.0.0, 9.1.143). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eb-csr (npm)

MAL-2025-192967

Immediate action

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

npm uninstall eb-csr

What this malware does

The package eb-csr 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

1.0.09.1.143

Indicators of compromise (SHA-256)

633a3693267851fd0c8eeee4cfc971fd7009c5c128d6a9ac0392d6ded3a8614f

bde17b1e5e6a9e071d031714e31335d93e040635afe32c1cb655b8892e8e2d3b

c988aaf2cec828bff1eb5e8554a4ecefe41b7fcdd6de1071360c08947c16c323

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for eb-csr (2 malicious versions).
If you installed it — respond
Remove eb-csr 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 eb-csr was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. eb-csr on npm has been identified as a malicious package (versions 1.0.0, 9.1.143 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-x757-3w6f-f9rmRLMA-2026-01268

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks eb-csr-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

Explore

All malware advisories How O3 detects malware Vulnerability database