apl-rive-renderer@100.0.0

apl-rive-renderer 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 apl-rive-renderer and 9 similar packages within two minutes on 2026-09-30, all with the same setup.js. --- ## Source: amazon-inspector (4c4d9c8cb631b53115adaa25c423d274f537639c711fcff7dcca6e22fa067269) apl-rive-renderer@100.0.0 declares a preinstall lifecycle script (setup.js) that fires automatically on npm install. The script collects installer host identifiers — os.hostname(), os.userInfo().username, process.cwd(), process.platform, process.arch, node version, and the configured npm registry — and POSTs them together with a static token to a hardcoded AWS API Gateway endpoint at https://s85r5k14qk.execute-api.us-east-1.amazonaws.com/prod/hook. The package presents itself as a trivial helper and has no documented functionality that would require phoning home with host reconnaissance. The name and version (100.0.0) are consistent with a dependency-confusion lure targeting an internal package name, and the beacon lets the operator identify which installer hosts (corporate build machines, developer workstations, CI runners) have resolved the public package instead of the intended internal one.