Which versions of nottuff15 are malicious?

The following npm versions of nottuff15 are flagged malicious: 1.7.7. Treat any of these as compromised.

How do I remediate nottuff15 if I installed it?

Remove nottuff15 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is nottuff15 part of a known attack campaign?

Yes — nottuff15 is associated with the IN-MAL-2026-006817 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect nottuff15 in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking nottuff15 and packages like it before any post-install script runs.

Malicious package

nottuff15npm

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

MAL-2026-5914

Immediate action

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

npm uninstall nottuff15

What this malware does

nottuff15 is one entry in a coordinated npm namespace-spam campaign. The tarball ships auto-publish.sh, a bash script that copies the package contents into ~95 differently-named tarballs (imillegal*, ishowfeet*, nottuff1..30, abuden*, ratelimitsucks*) and force-publishes each via npm publish; the package's own name 'nottuff15' appears in that list, confirming this release is generator output. Package metadata is placeholder (description: "package", empty author). The actual payload is a bundled SPA + ServiceWorker web-proxy (Scramjet) plus a 5.4MB WASM-curl bundle in j3ve9/ls3ez.mjs, distributed via npm but intended to be hosted as a static site — npm is being abused as a static-asset CDN. The package's main entry (sw.js) calls importScripts() on its first line, which is a browser ServiceWorker global undefined in Node, so require('nottuff15') throws a ReferenceError immediately — there is no functioning library here. The bundled index.html registers click/keydown/touchstart listeners that redirect users to https://abdct.com/ on first interaction (rate-limited via localStorage), and loads a remote script from https://cdn.21baseballacademy.com/script/jrqK2HPsliMjRW5Q.js — browser-side affiliate-redirect infrastructure under a tutoring-themed cover page. Twelve of the bundled JS assets are heavily obfuscated. No preinstall/install/postinstall/prepare hooks are declared, so there is no install-time auto-execution against the installer.

Malicious versions

1 flagged

1.7.7

Indicators of compromise (SHA-256)

ea629a411d1555cb4dbc80aa218539333aefce15e110ad0a5eaa16e4a58ab5f3

Frequently asked questions

No. nottuff15 on npm has been identified as a malicious package (version 1.7.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006817

References

npmjs.com

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection