Which versions of tw-theme-kit are malicious?

The following npm versions of tw-theme-kit are flagged malicious: 1.1.0. Treat any of these as compromised.

How do I remediate tw-theme-kit if I installed it?

Remove tw-theme-kit 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 activity or persistence.

I already installed tw-theme-kit — how do I know if it already compromised me?

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

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

Malicious package

tw-theme-kitnpm

tw-theme-kit is a confirmed malicious npm package (MAL-2026-5935) that executes malicious code on install (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tw-theme-kit (npm)

MAL-2026-5935

Immediate action

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

npm uninstall tw-theme-kit

What this malware does

The published entrypoints dist/index.cjs and dist/runtime.cjs contain an injected IIFE that assigns global.r = require and global.m = module, tags the host with campaign id 'A6-Orion-271', uses a string-shuffle helper to reconstruct the identifier 'constructor', then invokes Function() on a deshuffled obfuscated blob and immediately calls the resulting function. Any consumer that does require('tw-theme-kit') or import 'tw-theme-kit/runtime' triggers attacker-controlled code at load time with full Node capabilities (fs, child_process, net) exposed via the globals. This behavior is unrelated to the package's stated purpose (a Tailwind theme plugin) and matches the fingerprint of the 'Orion' obfuscated-loader campaign. The.mjs builds and source-maps embed the same obfuscated literal, so no entrypoint is safe.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

0144b9ea6743e481e49885f6375a8aa990e9a20bfc5da1148b7df59a9370736c

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for tw-theme-kit (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging tw-theme-kit across your stack and pipelines.
If you installed it — respond
Remove tw-theme-kit 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 activity or persistence.
Did it already run?
If tw-theme-kit 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 tw-theme-kit 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. tw-theme-kit on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006848

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tw-theme-kit-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

Explore

All malware advisories How O3 detects malware Vulnerability database