Which versions of @indriver-tools/whisperwind are malicious?

The following npm versions of @indriver-tools/whisperwind are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate @indriver-tools/whisperwind if I installed it?

Remove @indriver-tools/whisperwind from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @indriver-tools/whisperwind — how do I know if it already compromised me?

If @indriver-tools/whisperwind 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 @indriver-tools/whisperwind part of a known attack campaign?

Yes — @indriver-tools/whisperwind is associated with the RLMA-2026-04741, RLUA-2026-05876 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 @indriver-tools/whisperwind across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @indriver-tools/whisperwind (version 99.0.0).

Malicious package

@indriver-tools/whisperwindnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@indriver-tools/whisperwind is a confirmed malicious npm package (MAL-2026-7076) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @indriver-tools/whisperwind (npm)

MAL-2026-7076

Immediate action

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

npm uninstall @indriver-tools/whisperwind

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

2242fd1881294e079e1fcc3919b9d55cdc25114119dc724c70d82851c7a943dd

4339af8b7077dd55923d681adb01fd0b04ae197d90fc7d606cec2359d01ad45c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @indriver-tools/whisperwind (version 99.0.0).
If you installed it — respond
Remove @indriver-tools/whisperwind from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @indriver-tools/whisperwind 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. @indriver-tools/whisperwind on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04741RLUA-2026-05876

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @indriver-tools/whisperwind-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database