@wagni_bot/bsc-sdk versions 1.0.0, 1.1.0, 1.1.1, 1.1.3, 1.1.4, 1.1.5, and 1.2.0 are malicious typosquat packages targeting developers and CI environments. Upon installation, the package runs a postinstall lifecycle script that recursively scans the current working directory, the user's home directory, and ~/.ssh for files named id_rsa, id_ed25519, *.pem, *.key, *.cred, and .env. It also enumerates environment variables for keys containing sensitive keywords such as PRIVATE, SECRET, TOKEN, API_KEY, PASSWORD, MNEMONIC, SEED, WALLET, or AWS. The collected files and environment variables, along with hostname, username, and current working directory, are sent via HTTP POST to a hardcoded bare IP address (http://107.161.90.180:7777). The package exports an empty object and provides no legitimate BNB Smart Chain functionality, confirming its sole purpose is credential theft.

Any developer or CI system that installs this package risks having private SSH keys, PEM certificates, credential files, and sensitive environment variables exfiltrated to an attacker-controlled server. This can lead to unauthorized access to source code repositories, cloud services, and other critical infrastructure. The use of plaintext HTTP for data exfiltration indicates a lack of stealth but does not reduce the severity of the credential compromise.

No official patch or remediation is available since this is a malicious package rather than a vulnerability in legitimate software. The primary mitigation is to avoid installing @wagni_bot/bsc-sdk and to audit dependencies carefully to detect typosquatting. Remove any instances of this package from projects and CI pipelines immediately. Rotate any potentially compromised credentials, SSH keys, and certificates that may have been exposed. Use trusted package sources and enable package integrity verification where possible.