Malicious code in etoro-billing (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-16115
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (3c1ceae274b450706288722b9f6c049114593ef2671de93ac58c4fd4a7318c9a) 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).
- Source published
- 10 Sep 2026 04:43:30 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.