Which versions of etoro-client are malicious?

The following npm versions of etoro-client are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate etoro-client if I installed it?

etoro-client 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 etoro-client — how do I know if it already compromised me?

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

Yes — etoro-client is associated with the IN-MAL-2026-019910 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 etoro-client 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 etoro-client (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging etoro-client across your stack and pipelines.

Malicious package

etoro-clientnpm

etoro-client is a confirmed malicious npm package (MAL-2026-16119) that steals credentials and exfiltrates sensitive data (malicious version 999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in etoro-client (npm)

MAL-2026-16119

Immediate action

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

npm uninstall etoro-client

What this malware does

The preinstall lifecycle script in [email protected] unconditionally sends the installer's hostname, OS username, and current working directory to the hardcoded bare-IP endpoint http://209.126.81.147/etoro-depconf-poce346552f776f/npm/<host>/<user>/<cwd> over plain HTTP at npm install time. The package name combined with the implausibly high 999.0.0 version and the depconf path token indicate a dependency-confusion attack targeting an internal etoro-client package: publishing a high-version public namesake so that misconfigured resolvers pull this artifact instead of the private internal one. The preinstall beacon then confirms successful landing on a target and identifies the host, user, and build path.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

d31819832ff4b43fc9bc7bcd9f3439f71902802331ba6df3c3964c47765397e1

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 etoro-client (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging etoro-client across your stack and pipelines.
If you installed it — respond
etoro-client 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 etoro-client 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 etoro-client 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. etoro-client on npm has been identified as a malicious package (version 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019910

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks etoro-client-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