Which versions of timmytuffknuckles6 are malicious?

The following npm versions of timmytuffknuckles6 are flagged malicious: 1.1.7. Treat any of these as compromised.

How do I remediate timmytuffknuckles6 if I installed it?

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

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

Yes — timmytuffknuckles6 is associated with the GHSA-5m8p-jhm5-pm44, IN-MAL-2026-010228 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 timmytuffknuckles6 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 timmytuffknuckles6 (version 1.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging timmytuffknuckles6 across your stack and pipelines.

Malicious package

timmytuffknuckles6npm

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

MAL-2026-10389

Immediate action

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

npm uninstall timmytuffknuckles6

What this malware does

This package is not a Node.js library. package.json declares "main": "sw.js", a Service Worker that calls importScripts('./8cfc2/hgshm.js') — an API that does not exist in Node, so require('timmytuffknuckles6') throws immediately and the bundled obfuscated assets never execute on the installer's machine. The tarball contents are a school-unblocker / bare-mux web proxy bundle (index.html, multiple obfuscated assets/*.js files, WASM) wrapped in a Riverbend Tutoring cover page that, when served and visited in a browser, loads third-party scripts and opens popunders to external sites. There are no preinstall/install/postinstall lifecycle scripts, and no top-level Node-reachable code path that runs on install or require. The repository also ships auto-publish.sh, an author-run loop that rewrites package.json.name to timmytuffknuckles1..timmytuffknuckles10 and republishes the same payload under each name, polluting the npm namespace with ten clones. The script is not a lifecycle hook and does not run on install. The heavy obfuscation in assets/*.js is consistent with the Ultraviolet/bare-mux proxy framework these projects use, not with installer-side harm. Routing to human review because the package is registry-misuse (proxy webapp masquerading as an npm library, plus deliberate ten-name namespace squatting) even though it does not attack installers.

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

1 flagged

1.1.7

Indicators of compromise (SHA-256)

040a672027041512418b9d898bcf26a02f2fe75f50d918b546a3283c87ffd9ee

22ef6fa6c2b9f80d6a1f79e532a9d9ea083a1c662bc834d118879ba630842b0c

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 timmytuffknuckles6 (version 1.1.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging timmytuffknuckles6 across your stack and pipelines.
If you installed it — respond
timmytuffknuckles6 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 timmytuffknuckles6 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 timmytuffknuckles6 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. timmytuffknuckles6 on npm has been identified as a malicious package (version 1.1.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5m8p-jhm5-pm44IN-MAL-2026-010228

References

Credits

Amazon Inspector · finder

Detect & block this

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