Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

birch-css-utilsnpm

Advisory published Updated

birch-css-utils is a confirmed malicious npm package (MAL-2026-18331) that steals credentials and exfiltrates sensitive data (malicious versions 1.2.2, 1.3.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in birch-css-utils (npm)

MAL-2026-18331
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall birch-css-utils

What this malware does

Package advertises itself as a zero-runtime CSS theme kit and instructs installation as a Tailwind name-overlay (npm install -D tailwindcss@npm:birch-css-utils), but the published tarball contains ~760KB of heavily obfuscated JS (build-cache.mjs, cache-sweep.mjs, cache-warm.mjs) hidden behind a tailwindcss-theme-kit build cache manifest cover comment. The declared ./tokens export (tokens.mjs) top-level-imports cache-warm.mjs, so consumers that import birch-css-utils/tokens execute the obfuscated code on module load. The bundles use a hex-named XOR-encoded string array; decoding with key 0xED reveals AWS Sigv4 signing primitives (AWS4-HMAC-SHA256#Credential=), an AWS Access Key ID regex (^(?:AKIA|ASIA|ABIA|ACCA)[A-Z0-9]{16}$), and git identity env var names (GIT_AUTHOR_NAME, GIT_AUTHOR_DATE) embedded in the string array. A CSS custom-properties package has no legitimate use for AWS v4 signing material or an AWS key-ID matcher. The combination of Tailwind name-overlay install instructions, a README denying runtime JS, obfuscated executable bundles reachable from a public export, and decoded AWS credential-harvesting primitives constitutes a Tailwind imposter that steals AWS credentials from importing consumers.

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

Indicators of compromise (SHA-256)

55ac470ab3260611fd8b69f59b1d1faae26e80e1c7e9c243cb0b65db56d5c231
22815f068ecaf85065c389553848537859f9e37623285a9e71b3e81ee9e9b685
a5a07dab2c2f60304b678f04c55787fa5ab48282ce1ed46fb36f8dcdb8a713dc

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for birch-css-utils (2 malicious versions).

  2. If you installed it — respond

    birch-css-utils is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If birch-css-utils 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. birch-css-utils on npm has been identified as a malicious package (versions 1.2.2, 1.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-p597-2ggw-c82rIN-MAL-2026-021809IN-MAL-2026-021808

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks birch-css-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

birch-css-utils (npm) malicious package — MAL-2026-18331 | O3 Security