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

eth-loggernpm

Malicious code in eth-logger (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3029
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall eth-logger

What this malware does

The package eth-logger was found to contain malicious code.

The OpenSSF Package Analysis project identified 'eth-logger' @ 4.3.21 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged
4.3.204.3.21

Indicators of compromise (SHA-256)

028addf545d834096a4443644415ea2ec422310d4e413d6ded00fb87fdd4d74f
834f2df77f9e1df7adc62cd44dad73791aba5e7043373b2c5258691014b42e5d
843cae77c9aaf84bef1b7d5e46e27795d5203d2959a39b2797f0e1248b4995c7

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

  2. If you installed it — respond

    Remove eth-logger 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 eth-logger 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 eth-logger 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. eth-logger on npm has been identified as a malicious package (versions 4.3.20, 4.3.21 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks eth-logger-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.

eth-logger (npm) malicious package — MAL-2026-3029 | O3 Security