Which versions of etoro-charts are malicious?

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

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

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

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

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

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

Malicious package

etoro-chartsnpm

etoro-charts is a confirmed malicious npm package (MAL-2026-16118) 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-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

The package's preinstall.js runs automatically on npm install and issues an HTTP GET to a hardcoded bare IP (http://209.126.81.147/etoro-depconf-poce346552f776f/npm/<hostname>/<username>/<cwd>), embedding the installer's OS hostname (os.hostname()), OS username (os.userInfo().username), and current working directory (process.cwd()) as URL path segments. The package uses a generic 'eToro' brand name with a version pinned at 999.0.0, a pattern consistent with dependency-confusion attacks that aim to win resolution against an internal package of the same name. Installing the package causes installer-side identifiers to be sent in cleartext to an attacker-controlled endpoint.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

484ce8002025d68c4a60feca03aec63425a66b85e2465415a4fc5a29e3a61f43

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-charts (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-charts across your stack and pipelines.
If you installed it — respond
Remove etoro-charts 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-charts 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-charts 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-charts 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-019908

References

npmjs.com

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database