Malicious code in etoro-client (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-16119
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d31819832ff4b43fc9bc7bcd9f3439f71902802331ba6df3c3964c47765397e1) The preinstall lifecycle script in [email protected] unconditionally sends the installer's hostname, OS username, and current working directory to the hardcoded bare-IP endpoint http://209.126.81.147/etoro-depconf-poce346552f776f/npm/<host>/<user>/<cwd> over plain HTTP at `npm install` time. The package name combined with the implausibly high 999.0.0 version and the `depconf` path token indicate a dependency-confusion attack targeting an internal `etoro-client` package: publishing a high-version public namesake so that misconfigured resolvers pull this artifact instead of the private internal one. The preinstall beacon then confirms successful landing on a target and identifies the host, user, and build path.
- Source published
- 10 Sep 2026 04:44:04 UTC
- Source modified
- 10 Sep 2026 05:30:11 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.