Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

etoro-aggregatornpm

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

MAL-2026-16111
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall etoro-aggregator

What this malware does

[email protected] ships a preinstall.js that runs automatically on npm install and issues an HTTP GET to http://209.126.81.147/etoro-depconf-poce346552f776f/npm/<hostname>/<username>/<cwd>, encoding os.hostname(), os.userInfo().username, and process.cwd() as URL path segments. The version number (999.0.0), generic package name, and absence of any legitimate library code are consistent with a dependency-confusion lure: installing the package causes the installer's host identity to be sent to an attacker-controlled bare-IP endpoint over plaintext HTTP, providing reconnaissance for targeted follow-on attacks against organizations whose internal package names collide with this name.

Malicious versions

1 flagged
999.0.0

Indicators of compromise (SHA-256)

6e7805793fe0fa0f03f018a31574ec577e87f249231d9ada54cdf052395a65d1

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

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

  3. Did it already run?

    If etoro-aggregator 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.

  4. How O3 protects you

    O3 blocks etoro-aggregator 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-aggregator 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-019913

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks etoro-aggregator-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.

Explore

etoro-aggregator (npm) malicious package — MAL-2026-16111 | O3 Security