The npm package app-soda-layer 2.1.6 contains a malicious postinstall script (test.js) that runs automatically on npm install. It harvests sensitive files such as Solana keypairs (id.json), config.toml, and .env files from the host system and exfiltrates them to attacker-controlled HTTP endpoints. It also fetches an SSH public key from the attacker infrastructure and appends it to the user's ~/.ssh/authorized_keys file, changes ownership, and enables firewall rules to allow SSH access on port 22. The malware recursively scans the home directory or all logical drives on Windows for files matching attacker-supplied patterns, uploading any matches. The package was created specifically for this attack, published and unpublished within about 2.5 hours, and is no longer available on npm. The attack infrastructure and code reuse link it to a previously documented toolkit used in a February 2026 GitHub compromise. Indicators include the injected SSH key (ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIFYMx8MqdYTD/aZjqxmXo+9460+9EvsSjfiy9YAU+xwY) and specific API endpoints used for command and control.

Any system that installed app-soda-layer 2.1.6 is compromised. Sensitive credentials including Solana keypairs, configuration files, and environment secrets may have been exfiltrated to attacker servers. The attacker gains persistent remote access via an injected SSH public key and open port 22 firewall rule, allowing ongoing unauthorized access. This compromises confidentiality, integrity, and potentially availability of the affected host and any connected infrastructure relying on the stolen credentials.

The package was unpublished shortly after release and is no longer available from npm. Hosts that installed version 2.1.6 should be treated as compromised. Immediate actions include checking ~/.ssh/authorized_keys for the known malicious SSH key (ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIFYMx8MqdYTD/aZjqxmXo+9460+9EvsSjfiy9YAU+xwY) and removing it, verifying firewall rules for unexpected port 22 openings, and rotating all Solana keypairs, SSH keys, and secrets stored in .env files or other configuration files. Conduct a thorough forensic investigation to identify any further persistence or lateral movement. Since this is a malicious package rather than a vulnerability in legitimate software, no patch exists; remediation is incident response and secret rotation.