NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

nottuff27npm

Advisory published Updated

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

Malicious code in nottuff27 (npm)

MAL-2026-10352
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall nottuff27

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

2 flagged
1.1.71.7.7

Indicators of compromise (SHA-256)

2e05cd0ae18d00192d650d3ee5822b2d12e30b3227753ad5dd461de863dd5218
0b836372198329677623bb152dc7db76b249d842c0d10a3ec94d9ce2ae467827
30fd462e25edd41ac887ff116ca0cf649839a74978ad77a587f74a182683b62a

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for nottuff27 (2 malicious versions).

  2. If you installed it — respond

    nottuff27 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.

  3. Did it already run?

    If nottuff27 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. nottuff27 on npm has been identified as a malicious package (versions 1.1.7, 1.7.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-64q8-2rgw-gp3mIN-MAL-2026-010093IN-MAL-2026-010091

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks nottuff27-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

nottuff27 (npm) malicious package — MAL-2026-10352 | O3 Security