@rutxploit-sec/waves-button-pocnpm
@rutxploit-sec/waves-button-poc is a confirmed malicious npm package (MAL-2026-17290) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 2.0.0, 3.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @rutxploit-sec/waves-button-poc (npm)
What this malware does
@rutxploit-sec/[email protected] auto-executes host-identifier exfiltration on both npm install and require. package.json declares a preinstall script that runs node -e code which reads os.hostname() and os.userInfo().username and issues a plaintext HTTP GET to the hardcoded bare-IP endpoint http://80.225.217.8/poc/dep-confusion-proof.html, passing the package name, host, and user as query parameters. The declared main entry index.js repeats the same behavior at module top level, so any consumer that requires the package also beacons the same identifiers to the same IP. The scoped name and PoC framing are consistent with a dependency-confusion proof-of-concept, but the shipped code performs unauthenticated identifier collection from every installer regardless of intent, and the destination is an attacker-chosen bare IP over cleartext HTTP.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @rutxploit-sec/waves-button-poc (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @rutxploit-sec/waves-button-poc across your stack and pipelines.
If you installed it — respond
@rutxploit-sec/waves-button-poc 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 @rutxploit-sec/waves-button-poc was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @rutxploit-sec/waves-button-poc before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @rutxploit-sec/waves-button-poc-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.