--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (5a06d1b04d930608a5d15999711be4158b61d96a0f9c0c63353b3b25cd302c86) package.json declares `postinstall: node test.js`, but test.js is not present in the tarball — installation fails with MODULE_NOT_FOUND and no code executes against the installer. The shipped index.js is a one-line stub containing a broken `console(...)` call (no real functionality). Despite the placeholder content, the package declares axios, form-data, child_process, and os as dependencies — building blocks commonly used for exfiltration scripts — and ships with empty author/description metadata and a 'trial version' message. The current published version causes no installer harm because the referenced payload script is missing, but the shape (stub package + suspicious dep set + lifecycle hook pointing at an unshipped script) is consistent with a placeholder release that could be weaponized in a follow-up version. Routing for human review of maintainer identity and registry context. ## Source: ghsa-malware (9e771f79bc648994a4dc1e8bf9195230f1b6934984bcdb712269fe4c32a039ec) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

AI Analysis