none123s@0.1.0

package.json declares a `prepare` lifecycle script (`node index.js || true`) that auto-executes on `npm install`. index.js reads canonical installer-secret paths — ~/.ssh/id_rsa, ~/.ssh/id_ed25519, ~/.aws/credentials, ~/.config/gcloud/application_default_credentials.json, ~/.npmrc, ~/.pypirc, ~/.docker/config.json, ~/.gitconfig, and.env files walking up parent directories — plus a curated set of cloud/CI environment variables, and POSTs the contents to a hardcoded attacker-controlled ngrok tunnel at https://crabbing-thong-overhung.ngrok-free.dev/exfil. A separate `sendInitialPing` beacon posts host identifiers (hostname, platform, user, homedir, cwd, node version, npm lifecycle env, git user.email) to the same host at /ping to identify the victim. The `|| true` suffix silences errors so the install appears successful. This is a direct credential-theft supply-chain attack against any developer or CI system that installs the package. ## Source: ghsa-malware (87b3283e298b85e9f69225b2364436289724e45eab50b2e8903a07b26cefbf51) 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. ## Source: ossf-package-analysis (3a801f5544cdc371f8881fecdec89a94ddc07a32db29996aac125c9614300ce6) The OpenSSF Package Analysis project identified 'none123s' @ 0.1.7 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.