Which versions of etoro-charts are malicious?

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

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

etoro-charts establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

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

Yes — etoro-charts is associated with the IN-MAL-2026-019908, IN-MAL-2026-019993 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-charts across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for etoro-charts (2 malicious versions).

Malicious package

etoro-chartsnpm

Advisory published Sep 10, 2026Updated Sep 11, 2026

etoro-charts is a confirmed malicious npm package (MAL-2026-16118) that opens a backdoor for remote access (malicious versions 99.0.0, 999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in etoro-charts (npm)

MAL-2026-16118

Immediate action

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

npm uninstall etoro-charts

What this malware does

On npm install, preinstall.js runs automatically and sends the installer's hostname, username, platform, and current working directory via HTTP GET to http://209.126.81.147/etoro-nuget-verify1f8eaa57a875/npm/v2/<host>/<user>/<platform>/<cwd>, then executes whoami; id; hostname -f (or whoami /all on Windows) via child_process and POSTs the command output to the same hardcoded bare-IP endpoint over plain HTTP. The package.json advertises the package as an Internal service client library at version 99.0.0 with no real functional code beyond the preinstall hook, and the beacon path segment etoro-nuget-verify... targets an internal eToro namespace, matching the dependency-confusion recon pattern.

Malicious versions

2 flagged

99.0.0999.0.0

Indicators of compromise (SHA-256)

484ce8002025d68c4a60feca03aec63425a66b85e2465415a4fc5a29e3a61f43

e44aff5a1a0b68ff9c9b3456693ef1b8266dce7001dd8b6ff56bed428bbc7c5a

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for etoro-charts (2 malicious versions).
If you installed it — respond
etoro-charts establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If etoro-charts 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-charts on npm has been identified as a malicious package (versions 99.0.0, 999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019908IN-MAL-2026-019993

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks etoro-charts-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database