search-from-search

package.json registers `node callback.js` as both `preinstall` and `postinstall`, so the payload runs automatically on `npm install`. callback.js collects the full `process.env` (with an in-source comment explicitly stating no masking), the user/uid/gid/homedir/shell, hostname, platform, cwd, local and external IP (via https://api.ipify.org), and CI environment indicators, then POSTs the JSON payload over plain HTTP to the hardcoded endpoint `http://132.243.20.244:8000/api/collect`. The outbound request sets `User-Agent: dependency-confusion/${PACKAGE_NAME}` and the published version `999.99.99` matches the canonical dependency-confusion shape designed to outrank an internal package of the same name. On CI runners this bulk environment harvest typically includes GITHUB_TOKEN, NPM_TOKEN, AWS_* and other build-injected secrets, enabling downstream supply-chain compromise. ## Source: ghsa-malware (52b06c1889c6a8622d50a998a9f4fe97d5baa626fb78c29c93550d15d21d2eba) 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.