Which versions of etoro-analytics are malicious?

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

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

Remove etoro-analytics 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.

I already installed etoro-analytics — how do I know if it already compromised me?

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

Yes — etoro-analytics is associated with the IN-MAL-2026-019912 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for etoro-analytics (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-analytics across your stack and pipelines.

Malicious package

etoro-analyticsnpm

etoro-analytics is a confirmed malicious npm package (MAL-2026-16112) that executes malicious code on install (malicious version 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

The package's preinstall lifecycle script runs automatically on npm install and sends the installer's hostname, OS username, and current working directory to a hardcoded remote host at http://209.126.81.147 over plain HTTP, embedding the values as URL path segments under /etoro-depconf-poce346552f776f/npm/. The destination is a bare IP address, not configurable, and unrelated to any legitimate publisher infrastructure. The 999.0.0 version and eToro-themed name are consistent with a dependency-confusion lure targeting an internal package name.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

a87dfbd5f51b30470e8d1df702e746f7c8141fdaafab2237fd1f2ef4897d9ae5

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for etoro-analytics (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-analytics across your stack and pipelines.
If you installed it — respond
Remove etoro-analytics 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.
Did it already run?
If etoro-analytics 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-analytics 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-analytics 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-019912

References

npmjs.com

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 malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database