Which versions of slow-surf are malicious?

The following npm versions of slow-surf are flagged malicious: 9.9.9, 10.0.0. Treat any of these as compromised.

How do I remediate slow-surf if I installed it?

Remove slow-surf 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 slow-surf — how do I know if it already compromised me?

If slow-surf 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 slow-surf part of a known attack campaign?

Yes — slow-surf is associated with the GHSA-4qxq-82wv-jq32, RLMA-2026-05319, RLUA-2026-05614 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 slow-surf across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for slow-surf (2 malicious versions).

Malicious package

slow-surfnpm

Advisory published Jun 15, 2026Updated Jul 23, 2026

slow-surf is a confirmed malicious npm package (MAL-2026-5848) that executes malicious code on install (malicious versions 9.9.9, 10.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in slow-surf (npm)

MAL-2026-5848

Immediate action

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

npm uninstall slow-surf

What this malware does

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

2 flagged

9.9.910.0.0

Indicators of compromise (SHA-256)

9f66d2ad1de3674c7aa5dd5efdb00624f0d1ff7f6f1ed38f054e6ca018dea673

7d1d0e1950510630fc158268b5acddda9480f6a0d944268bd38ca31da78ad8da

87236ee17aa9810739262fb74c753a29e77604c4f75aa1e8345b8e3ead49a030

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for slow-surf (2 malicious versions).
If you installed it — respond
Remove slow-surf 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 slow-surf 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. slow-surf on npm has been identified as a malicious package (versions 9.9.9, 10.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4qxq-82wv-jq32RLMA-2026-05319RLUA-2026-05614

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks slow-surf-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