Which versions of rpc-endpoint-rotator are malicious?

The following npm versions of rpc-endpoint-rotator are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate rpc-endpoint-rotator if I installed it?

rpc-endpoint-rotator is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed rpc-endpoint-rotator — how do I know if it already compromised me?

If rpc-endpoint-rotator 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.

Is rpc-endpoint-rotator part of a known attack campaign?

Yes — rpc-endpoint-rotator is associated with the IN-MAL-2026-014835 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 rpc-endpoint-rotator across my projects, lockfiles, and CI pipelines?

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

Malicious package

rpc-endpoint-rotatornpm

rpc-endpoint-rotator is a confirmed malicious npm package (MAL-2026-12431) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rpc-endpoint-rotator (npm)

MAL-2026-12431

Immediate action

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

npm uninstall rpc-endpoint-rotator

What this malware does

index.js schedules a top-level POST on module load to https://enjbyg3xk8l.x.pipedream.net/beacon carrying the entire process.env plus OS hostname, username, and home directory. The beacon fires unconditionally on require() and is unrelated to the package's advertised RPC-endpoint-rotation purpose. Surrounding exported helpers (keccak256, toChecksumAddress, formatUnits) serve as a cover story; a source comment labels the top-level code as a hidden periodic env-data beacon. Whole-environment transmission captures any credentials the requiring process has in env (cloud keys, CI tokens, provider secrets).

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7eda47a0d1da23b08d63a5fa4339234b9a19bc7aedf7b74d060731b24841be2a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rpc-endpoint-rotator (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rpc-endpoint-rotator across your stack and pipelines.
If you installed it — respond
rpc-endpoint-rotator is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If rpc-endpoint-rotator 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.
How O3 protects you
O3 blocks rpc-endpoint-rotator 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. rpc-endpoint-rotator on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014835

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks rpc-endpoint-rotator-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database