Malicious code in twilio-functions (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-12813
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (ea71d301e90ede6f86f259e827a1cb61ad0b4b0166b70281bdf7896f726eea31) On npm install, the package's postinstall script executes index.js, which collects host identifiers (os.hostname(), os.userInfo().username, os.homedir(), process.cwd(), os.platform(), os.arch(), and selected environment variables) and POSTs them as JSON to a hardcoded webhook.site collection URL (https://webhook.site/42ce0f0e-a0a0-41b5-b157-1c0f918e064f). On network error, the code falls back to a DNS callback against an interactsh-style subdomain at 2b22ede784d5.oast.fun. Package metadata (name `twilio-functions` mimicking the Twilio SDK namespace, version 99.99.99, empty description) is consistent with a typosquat / dependency-confusion lure whose only on-install effect is the outbound reconnaissance beacon.
- Source published
- 5 Aug 2026 13:11:02 UTC
- Source modified
- 9 Sep 2026 03:30:13 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.