MAL-2026-16111 Malicious code in etoro-aggregator (npm)
Malicious package
Published
MAL-2026-16111 is a malicious package: etoro-aggregator (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-16111/ (Markdown: https://insights.sbomify.com/MAL-2026-16111/index.md)
- Package
- etoro-aggregator
- Registry
- npm
What is MAL-2026-16111?
MAL-2026-16111 is a malicious package in etoro-aggregator, published on 10 Sep 2026.
Official description
The package's preinstall.js lifecycle script executes automatically on
npm install and performs reconnaissance on the installer host. It collects hostname, username, current working directory, platform, and the output of OS commands including whoami /all, ipconfig /all / ifconfig, tasklist / ps aux, directory listings of /, C:\, and the user's home, and a dump of environment variables. The collected data is transmitted via HTTP GET and POST to the hardcoded bare IP endpoint http://209.126.81.147/etoro-nuget-verify1f8eaa57a875/v4/.... The package's declared main is an empty stub and its description ("Internal service client library") combined with the implausibly high version number 99.0.2 is consistent with a dependency-confusion attack targeting an internal etoro-aggregator name. The manifest plus the preinstall script constitute the entire payload; installing the package leaks installer host identity, network configuration, filesystem structure, and environment variables (which routinely contain credentials and tokens) to an attacker-controlled endpoint.What should I do about MAL-2026-16111?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.