ts-linting-builder

Details

---
_-= Per source details. Do not edit below this line.=-_

## Source: amazon-inspector (c719aef78218f6b59b9f209c41eff610782c86c2ced5aeabe288218ac3c4f880)
On npm install, the package's postinstall script (test.js) invokes routines in index.js that recursively scan the current working directory and the user's home directory (on Windows, all non-C: drives plus C:\Users) for files matching.env, id.json, config.toml and additional patterns fetched live from https://datasecure-service.vercel.app/api/scan-patterns. Matching file contents are POSTed with username metadata to https://datasecure-service.vercel.app/api/v1, harvesting Solana-style wallet keys (id.json), environment files, and arbitrary config secrets. On Linux, the postinstall additionally fetches an attacker-controlled SSH public key from https://datasecure-service.vercel.app/api/ssh-key, appends it to ~/.ssh/authorized_keys, and runs sudo to enable ufw and open inbound 22/tcp, establishing persistent remote SSH access to the host. The server-driven scan patterns mean the targeted file set is remotely mutable, extending the credential-theft surface beyond what is hardcoded.

## Source: ghsa-malware (a94bed4fe706f9120b29ea2b3168223045294bb0c233c35c1cae913b28e5c76e)
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.

Compromised versions (1)

• 2.1.2

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.