Malicious code in alelo-sdk (npm)

CISA 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.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4e7ed1d4017e58a9911a0cfee5d1cf8122a2ac28779a36fdf3ef74484f048748) [email protected] ships lifecycle scripts that harvest installer data and POST it to a hardcoded bare-IP endpoint (209.99.185.109) with TLS certificate verification disabled. preinstall.js collects hostname, username, platform, cwd, and the full process.env and sends the JSON to https://209.99.185.109/preinstall. The postinstall path (index.js) additionally reads.env,.npmrc, and parent-directory.env files, executes whoami/id, and POSTs the collected content to https://209.99.185.109/postinstall..npmrc typically contains npm publish tokens and.env files typically contain cloud and API credentials, so any environment where this package is installed (developer workstation or CI) has its secrets extracted. Package metadata (name 'alelo-sdk', version 99.0.0, description 'internal utilities', author 'Alelo Dev Team') is the canonical dependency-confusion shape targeting a private 'alelo' internal scope with an inflated version number.

Source published

14 Aug 2026 14:12:58 UTC

Source modified

24 Sep 2026 09:30:07 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.