@limebike/frontend-core-api

Package squats the @limebike npm scope and ships a preinstall/postinstall hook (`node index.js`) that, on `npm install`, collects hostname, non-internal network interface addresses, current working directory, directory listings of cwd / /app /../../ /../../../, and the contents of /app/package.json, then POSTs that JSON over plain HTTP to http://poc.khz.bar/install (index.js:46-52). README states 'Claimed by dphoeniixx', a handle associated with dependency-confusion research, but regardless of stated intent every installer whose CI mistakenly resolves the @limebike scope to the public registry leaks internal hostnames, internal network IPs, and the parent project's package.json to an attacker-controlled endpoint at install time. ## Source: ghsa-malware (ee42d28817c6c33d00e1bba45629091411b7d9591a5d941419f44e171cc99a58) 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.