Which versions of abuden213 are malicious?

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

How do I remediate abuden213 if I installed it?

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

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

Yes — abuden213 is associated with the GHSA-pqjq-v3c7-738r, IN-MAL-2026-009968, IN-MAL-2026-009966, IN-MAL-2026-009970 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 abuden213 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 abuden213 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging abuden213 across your stack and pipelines.

Malicious package

abuden213npm

abuden213 is a confirmed malicious npm package (MAL-2026-10256) that opens a backdoor for remote access (malicious versions 1.1.7, 1.7.7, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in abuden213 (npm)

MAL-2026-10256

Immediate action

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

npm uninstall abuden213

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)

af2b4d3ac71c785b441203ff3096f1bb5cdcb6d9c197139976b8198e194e3834

a014a046e0516c12f5b1d7dcebebc2451633c4987fd3c96aae43229501ede141

8eb875b9587ee02772fa7f93c778bfbd0eb897c0758ce122160b6576201f14e7

9d1e4967a3469e0c33f2496085591e8bed13e3ec7b692ae95966343a9ec5acfb

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 abuden213 (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging abuden213 across your stack and pipelines.
If you installed it — respond
abuden213 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 abuden213 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 abuden213 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. abuden213 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-pqjq-v3c7-738rIN-MAL-2026-009968IN-MAL-2026-009966IN-MAL-2026-009970

References

Credits

Amazon Inspector · finder

Detect & block this

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