Which versions of etoro-billing are malicious?

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

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

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

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

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

Malicious package

etoro-billingnpm

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

MAL-2026-16115

Immediate action

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

npm uninstall etoro-billing

What this malware does

On npm install, the package's preinstall lifecycle hook executes preinstall.js, which reads os.hostname(), os.userInfo().username, and process.cwd() and issues an HTTP GET to http://209.126.81.147/etoro-depconf-poce346552f776f/npm/<hostname>/<username>/<cwd>. The destination is a hardcoded bare-IP over plain HTTP, unrelated to any documented eToro infrastructure. index.js is an empty stub (module.exports = {}), so the only effect of installing this package is the identifier beacon. The package name claims eToro affiliation and is published as version 999.0.0, a high-version pattern used to win resolution against an internal package of the same name (dependency confusion).

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

3c1ceae274b450706288722b9f6c049114593ef2671de93ac58c4fd4a7318c9a

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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