Which versions of eth-slint are malicious?

The following npm versions of eth-slint are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate eth-slint if I installed it?

eth-slint is a typosquat — you almost certainly intended a legitimately-named package. Remove eth-slint, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed eth-slint — how do I know if it already compromised me?

If eth-slint 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 eth-slint part of a known attack campaign?

Yes — eth-slint is associated with the GHSA-xp97-c4c4-7928, IN-MAL-2026-011155 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 eth-slint 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 eth-slint (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 eth-slint across your stack and pipelines.

Malicious package

eth-slintnpm

eth-slint is a confirmed malicious npm package (MAL-2026-11034) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eth-slint (npm)

MAL-2026-11034

Immediate action

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

npm uninstall eth-slint

What this malware does

eth-slint is a typosquat of web3-core-subscriptions. src/index.js contains a clean 2119-byte copy of the legitimate web3.js subscriptions module, while lib/index.js (the shipped main entry) contains that same code plus an appended ~149KB obfuscated blob passed to a top-level Function(...) constructor with a custom decoder routine, signed-int mixing table, and hex-escaped byte array. The Function() invocation fires at module load time, executing the decoded payload on the installer's host whenever the package is required or imported. The payload is present only in lib/, not in src/, indicating post-build injection rather than a normal compilation artifact.

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

a547e155b232bc3164db9fc1f7de92bf70a5f1ad02e277a6c9b272d47f48e00d

4bdbbc1ccc748bfe5ad640ed4e54ed5285a526a78a198ac2bf64727b7730d54d

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eth-slint (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 eth-slint across your stack and pipelines.
If you installed it — respond
eth-slint is a typosquat — you almost certainly intended a legitimately-named package. Remove eth-slint, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If eth-slint 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 eth-slint 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-slint 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

GHSA-xp97-c4c4-7928IN-MAL-2026-011155

References

Credits

Amazon Inspector · finder

Detect & block this

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