Malicious code in alexa-cybertron-team-code-review-agent (npm)

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

alexa-cybertron-team-code-review-agent is a dependency-confusion package: it takes a name that looks like an internal project, uses an inflated version (100.0.0) so it outranks private-registry versions, and runs `node setup.js || true` as a preinstall script on npm install. setup.js sends the hostname, username, working directory, OS, architecture, Node.js version and configured npm registry, with a per-package tracking token, in an HTTPS POST to `https://s85r5k14qk.execute-api.us-east-1.amazonaws.com/prod/hook`. The npm account amel10 published alexa-cybertron-team-code-review-agent and 9 similar packages within two minutes on 2026-09-30, all with the same setup.js. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (528ef9e111300abbee80027c6f51261639e05e482a6723919c9dba0f5e317c2c) npm package [email protected] presents itself as a one-line titleCase utility (index.js is an inert stub) but declares a preinstall lifecycle hook `node setup.js` that runs automatically on `npm install`. setup.js collects installer host and user identifiers - os.hostname(), os.userInfo().username, process.cwd(), process.platform, process.arch, node version, and the configured npm registry - together with a hardcoded token, and POSTs them via https.request to the hardcoded endpoint https://s85r5k14qk.execute-api.us-east-1.amazonaws.com/prod/hook. The package name namespaces an internal-sounding team (`alexa-cybertron-team-...`) and is published at version 100.0.0, a shape consistent with a dependency-confusion probe designed to win resolution against a private internal package and report back which victim environments installed it. There is no relationship between the advertised titleCase functionality and the install-time host reconnaissance beacon.

Source published

30 Sep 2026 07:11:21 UTC

Source modified

4 Oct 2026 23:45:17 UTC

Observed 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

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.