What does the @rutxploit-sec/waves-icons malware do?

@rutxploit-sec/waves-icons is a dependency-confusion proof-of-concept squatting the internal scope name @waves/icons. Its package.json declares a preinstall lifecycle hook that runs inline Node code (node -e...) which reads os.hostname() and os.userInfo().username and transmits them via http.get to a hardcoded beacon URL http://127.0.0.1:8099/?pkg= &host= &user= . The hook also prints a marker string '[BUGBOUNTY] @waves/icons dep confusion EXECUTED' to confirm execution. The code path runs automatically on npm install on any machine that resolves this squatted scope, collecting installer host identifiers and sending them to an attacker-chosen endpoint. Although the beacon is cu

Which versions of @rutxploit-sec/waves-icons are malicious?

The following npm versions of @rutxploit-sec/waves-icons are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @rutxploit-sec/waves-icons if I installed it?

@rutxploit-sec/waves-icons establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed @rutxploit-sec/waves-icons — how do I know if it already compromised me?

If @rutxploit-sec/waves-icons 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.

Is @rutxploit-sec/waves-icons part of a known attack campaign?

Yes — @rutxploit-sec/waves-icons is associated with the IN-MAL-2026-020684 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @rutxploit-sec/waves-icons across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @rutxploit-sec/waves-icons (version 1.0.0).

Malicious package

@rutxploit-sec/waves-iconsnpm

Advisory published Sep 29, 2026Updated Sep 29, 2026

@rutxploit-sec/waves-icons is a confirmed malicious npm package (MAL-2026-17291) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @rutxploit-sec/waves-icons (npm)

MAL-2026-17291

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @rutxploit-sec/waves-icons

What this malware does

@rutxploit-sec/waves-icons is a dependency-confusion proof-of-concept squatting the internal scope name @waves/icons. Its package.json declares a preinstall lifecycle hook that runs inline Node code (node -e...) which reads os.hostname() and os.userInfo().username and transmits them via http.get to a hardcoded beacon URL http://127.0.0.1:8099/?pkg=<pkg>&host=<host>&user=<user>. The hook also prints a marker string '[BUGBOUNTY] @waves/icons dep confusion EXECUTED' to confirm execution. The code path runs automatically on npm install on any machine that resolves this squatted scope, collecting installer host identifiers and sending them to an attacker-chosen endpoint. Although the beacon is currently set to loopback (127.0.0.1), it is a hardcoded destination the publisher controls and can trivially be changed or paired with an active listener; the install-time execution, host reconnaissance, and unsolicited outbound HTTP are present as published.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

bdeb076eee35958fd0520e7f9cca9d361c47f02cb81c73288609ecdfb60bdbb1

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for @rutxploit-sec/waves-icons (version 1.0.0).
If you installed it — respond
@rutxploit-sec/waves-icons establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @rutxploit-sec/waves-icons 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

No. @rutxploit-sec/waves-icons on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020684

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @rutxploit-sec/waves-icons-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database