Which versions of etoro-analytics are malicious?

The following npm versions of etoro-analytics are flagged malicious: 99.0.0, 99.0.2, 999.0.0. Treat any of these as compromised.

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

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

If etoro-analytics was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is etoro-analytics part of a known attack campaign?

Yes — etoro-analytics is associated with the IN-MAL-2026-019912, IN-MAL-2026-020001, IN-MAL-2026-019998 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-analytics across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for etoro-analytics (3 malicious versions).

Malicious package

etoro-analyticsnpm

Advisory published Sep 10, 2026Updated Sep 11, 2026

etoro-analytics is a confirmed malicious npm package (MAL-2026-16112) that steals credentials and exfiltrates sensitive data (malicious versions 99.0.0, 99.0.2, 999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in etoro-analytics (npm)

MAL-2026-16112

Immediate action

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

npm uninstall etoro-analytics

What this malware does

[email protected] ships a preinstall lifecycle script (preinstall.js) that automatically runs on npm install. The script collects installer host identifiers (hostname, username, cwd, platform) and issues an initial HTTP GET to http://209.126.81.147/etoro-nuget-verify1f8eaa57a875/v4/<host>/<user>/<platform>/<cwd>. It then invokes child_process.execSync on platform-branched reconnaissance commands (whoami /all, ipconfig /all, tasklist on Windows; whoami, ifconfig, ps aux, env on POSIX) plus home/root directory listings and POSTs the output back to the same hardcoded bare-IP endpoint over plain HTTP. The package name, implausibly high version number (99.0.2), and canary-token URL path are consistent with a dependency-confusion beacon targeting an internal etoro package namespace.

Malicious versions

3 flagged

99.0.099.0.2999.0.0

Indicators of compromise (SHA-256)

a87dfbd5f51b30470e8d1df702e746f7c8141fdaafab2237fd1f2ef4897d9ae5

5273aff85f2243e73b1fb50f228c752d9c22ada7f7d17abae33215e2020e13f9

bfe27d37497e77c8f0eca9105a6b64c646c7ef1439c05ec50edaf40215037f92

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for etoro-analytics (3 malicious versions).
If you installed it — respond
etoro-analytics 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-analytics was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. etoro-analytics on npm has been identified as a malicious package (versions 99.0.0, 99.0.2, 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019912IN-MAL-2026-020001IN-MAL-2026-019998

References

Credits

Amazon Inspector · finder

Detect & block this

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