What does the etoro-builders malware do?

The package's preinstall lifecycle script (preinstall.js) reads the installer's OS hostname, username, and current working directory via os.hostname(), os.userInfo().username, and process.cwd(), encodes them into a URL path, and issues an HTTP GET to a hardcoded bare-IP endpoint at http://209.126.81.147/etoro-depconf-.../npm/ / / . The package name 'etoro-builders' combined with the implausibly high version 999.0.0 and minimal placeholder contents is consistent with a dependency-confusion payload designed to win resolution against a private internal package and beacon successful installs to the operator. Installer host identifiers leave the machine at npm install time t

Which versions of etoro-builders are malicious?

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

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

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

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

Yes — etoro-builders is associated with the IN-MAL-2026-019914 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-builders 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-builders (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-builders across your stack and pipelines.

Malicious package

etoro-buildersnpm

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

Malicious code in etoro-builders (npm)

MAL-2026-16116

Immediate action

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

npm uninstall etoro-builders

What this malware does

The package's preinstall lifecycle script (preinstall.js) reads the installer's OS hostname, username, and current working directory via os.hostname(), os.userInfo().username, and process.cwd(), encodes them into a URL path, and issues an HTTP GET to a hardcoded bare-IP endpoint at http://209.126.81.147/etoro-depconf-.../npm/<hostname>/<username>/<cwd>. The package name 'etoro-builders' combined with the implausibly high version 999.0.0 and minimal placeholder contents is consistent with a dependency-confusion payload designed to win resolution against a private internal package and beacon successful installs to the operator. Installer host identifiers leave the machine at npm install time to a third-party bare-IP host over cleartext HTTP.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

c9210fb131a2f661ae1d656fa461d45c6c54377179aecba06e6a07b4f357a00b

Detection & response playbook

Backdoor / remote access

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks etoro-builders-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