Which versions of ratelimitsucks2 are malicious?

The following npm versions of ratelimitsucks2 are flagged malicious: 1.1.4, 1.1.7, 1.7.7, 2.0.0. Treat any of these as compromised.

How do I remediate ratelimitsucks2 if I installed it?

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

If ratelimitsucks2 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.

Is ratelimitsucks2 part of a known attack campaign?

Yes — ratelimitsucks2 is associated with the GHSA-8cfc-7p3v-8pjr, IN-MAL-2026-010159, IN-MAL-2026-010162, IN-MAL-2026-010161, IN-MAL-2026-010164 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 ratelimitsucks2 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ratelimitsucks2 (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ratelimitsucks2 across your stack and pipelines.

Malicious package

ratelimitsucks2npm

Malicious code in ratelimitsucks2 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10367

Immediate action

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

npm uninstall ratelimitsucks2

What this malware does

The tarball ships auto-publish.sh, a script that republishes the same payload under ~100 distinct npm names (ishowfeet1-ishowfeet20, nottuff1-nottuff30, abuden*, imillegal*, ratelimitsucks*, etc/) by rewriting package.json.name and running npm publish --silent in a loop — namespace-spam infrastructure shipped inside the package itself. The package's declared main is sw.js, a browser Service Worker (importScripts('./8cfc2/hgshm.js'), self.addEventListener('install'|'activate'|'fetch'|'message')) that throws immediately if loaded from Node. The shipped assets are a heavily obfuscated Ultraviolet/bare-mux web-proxy frontend with an index.html themed as "Riverbend Tutoring" that hides a popunder redirect to https://abdct.com/ on click/keydown/touchstart. package.json declares no preinstall/install/postinstall/prepare hooks, and require('ishowfeet9') from Node fails before any code runs, so a Node installer experiences no auto-execution. The harm is registry abuse (mass-publication of a misleading name family) and a browser-side proxy/popunder served to whoever later loads these static assets — not installer-side compromise. Routing to human review for namespace-abuse adjudication.

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

4 flagged

1.1.41.1.71.7.72.0.0

Indicators of compromise (SHA-256)

74011fae0c4ececd52cfd27e06b67efa9693735d66c6715837224e84c004bdb0

0d35482838ac389f7af960c113776867c9c5a83b1995ad7ece20fd26b71918ce

9bf993e68be5f0451150d4cb018eb0150c8421aeaa5ba205dc6a87493f2b45bd

a87610ed5d2b5fea36c953265f26730f6c1b0fb87c00cbbd9a49d979f75d2377

e4e767809f7b8fb0a395f3ff28f53d0a12d67d7a66a1823f9df5ddbcf1d29131

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ratelimitsucks2 (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ratelimitsucks2 across your stack and pipelines.
If you installed it — respond
ratelimitsucks2 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 ratelimitsucks2 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 ratelimitsucks2 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

No. ratelimitsucks2 on npm has been identified as a malicious package (versions 1.1.4, 1.1.7, 1.7.7, 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8cfc-7p3v-8pjrIN-MAL-2026-010159IN-MAL-2026-010162IN-MAL-2026-010161IN-MAL-2026-010164

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ratelimitsucks2-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