banana-standnpm
Advisory published Updated
banana-stand is a confirmed malicious npm package (MAL-2026-4495) that steals credentials and exfiltrates sensitive data (malicious version 9.9.11). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in banana-stand (npm)
What this malware does
On npm install, the package's install lifecycle hook runs node index.js, which loads lib/core.js. That module reads os.userInfo().username, os.hostname(), and the basename of process.cwd(), then issues a dns.resolve4 lookup for lwbanana.<username>.<hostname>.<cwd>.<unixtime>.oob.sl4x0.xyz, smuggling host identifiers out-of-band via DNS to an author-controlled domain. The same path also fires on require('banana-stand') because main points at the same entry. Strings used to construct the exfil (os, dns, userInfo, hostname, cwd, resolve4, and the destination domain oob.sl4x0.xyz) are concealed as String.fromCharCode byte arrays in lib/6ad264.js and lib/b02e30.js and decoded at runtime, indicating intentional concealment of the exfiltration channel.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for banana-stand (version 9.9.11).
If you installed it — respond
banana-stand is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If banana-stand was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- ReversingLabs · finder
Detect & block this
O3 blocks banana-stand-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.