Which versions of speed3 are malicious?

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

How do I remediate speed3 if I installed it?

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

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

Yes — speed3 is associated with the GHSA-2qw4-g5r6-hcr5, IN-MAL-2026-010211, IN-MAL-2026-010217 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 speed3 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 speed3 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging speed3 across your stack and pipelines.

Malicious package

speed3npm

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

MAL-2026-10384

Immediate action

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

npm uninstall speed3

What this malware does

[email protected] is not a functional Node package. package.json declares main: sw.js, but sw.js is a browser ServiceWorker (importScripts('./8cfc2/hgshm.js'), self.addEventListener('install'|'activate'|'fetch'|'message')) — require('speed3') throws immediately in Node, so there is no install-time or import-time code-execution path that touches the installer. The tarball bundles a static web-proxy frontend (bare-mux / Ultraviolet / Scramjet stack, confirmed by bare-mux: running v2.1.9 in d1g0y/xsv4z.js) plus an index.html popunder that opens https://abdct.com/ on user click/keydown/touchstart with a 15-minute cooldown — browser behavior for visitors of the deployed site, not npm consumers. The tarball also ships auto-publish.sh (BASE="speed"; TOTAL=5; PARALLEL=2;... pkg.name = '$NAME'; npm publish --silent), and the recursive nested directories tmp_speed2/ and tmp_speed2/tmp_speed1/ inside the published tarball are direct evidence the author ran the script to mass-publish speed1..speed5 typosquat names. The many heavily-obfuscated assets/*.js files are browser bundles loaded by the deployed index.html and are not reachable from any Node entry point. Routing to human review for namespace-abuse adjudication: the lure is non-functional and the bundled obfuscated assets cannot be fully audited, so a reviewer should confirm the typosquat campaign and request takedown across the speedN family.

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

Indicators of compromise (SHA-256)

822efae3c35e02231a2ba2a90b4abded866be45f031ffda19be12b984988b77d

6b80af0db1256f63f83fad514fe6b535d6af57513431058efc38136dddd18022

9c21af55681d718d8d66365b06788612df407b9ed5ba29102dc833d79479632e

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

Campaign

GHSA-2qw4-g5r6-hcr5IN-MAL-2026-010211IN-MAL-2026-010217

References

Credits

Amazon Inspector · finder

Detect & block this

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