Which versions of abuden215 are malicious?

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

How do I remediate abuden215 if I installed it?

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

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

Yes — abuden215 is associated with the GHSA-27j2-xj3j-rm76, IN-MAL-2026-009963, IN-MAL-2026-009965, IN-MAL-2026-009962 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 abuden215 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 abuden215 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging abuden215 across your stack and pipelines.

Malicious package

abuden215npm

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

MAL-2026-10258

Immediate action

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

npm uninstall abuden215

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

3 flagged

1.1.71.7.72.0.0

Indicators of compromise (SHA-256)

fef8ffeb8f242351d67a083616f2d63a9044c53b47a948cc137cf817ddfbb4ec

895382f96e91ecd3b6a78cac09b905becc2692fef044eacd9ce4d5cb18327b5f

f96533ebd3d5fcc30a1343f935a5aa8d33adc1862f1ce63edcfa30c8c08dbb04

075082fd0d0f68f7b49bed8f369cfd64a4e9d6eddba1e7c94637dc1cad607048

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 abuden215 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging abuden215 across your stack and pipelines.
If you installed it — respond
abuden215 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 abuden215 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 abuden215 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. abuden215 on npm has been identified as a malicious package (versions 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-27j2-xj3j-rm76IN-MAL-2026-009963IN-MAL-2026-009965IN-MAL-2026-009962

References

Credits

Amazon Inspector · finder

Detect & block this

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