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

eth-ticknpm

eth-tick is a confirmed malicious npm package (MAL-2026-6837) that executes malicious code on install (malicious versions 7.4.17, 7.4.18). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eth-tick (npm)

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

What this malware does

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
7.4.177.4.18

Indicators of compromise (SHA-256)

f96638eb8282b1eccbe4d7c1b1076340ac1b870d325856e2ad5415c2bf2737eb
a751a7ef8876cd791f5dfb336d8e4f0563839686faefad3fff09b0fb9a2f2dbe

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-tick (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-tick across your stack and pipelines.

  2. If you installed it — respond

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

Campaign

GHSA-cqqh-cj4r-mwfrRLMA-2026-05076

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks eth-tick-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

eth-tick (npm) malicious package — MAL-2026-6837 | O3 Security