Malicious code in alloy-graphql (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-16063
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (80ee3815d12ec95aedb4bbe0d3de5c516e99163ca1eba52c2a3de7038b9a2ac0) package.json declares a preinstall hook that runs index.js on npm install. The script collects hostname, username, home directory, DNS servers, current working directory, and package.json contents, and reads /etc/passwd and /etc/hosts from the installer's host. The collected data is HTTPS-POSTed to a hardcoded Burp Collaborator subdomain at ipbtwv9063nc5hvhodh0s4u9x03rrhf6.oastify.com. The package has no advertised functionality beyond this exfiltration payload.
- Source published
- 9 Sep 2026 01:40:48 UTC
- Source modified
- 9 Sep 2026 02:00:04 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.