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

@brandkit/themenpm

Advisory published Updated

@brandkit/theme is a confirmed malicious npm package (MAL-2026-20041) that executes malicious code on install (malicious versions 2.4.1, 2.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @brandkit/theme (npm)

MAL-2026-20041
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @brandkit/theme

What this malware does

@brandkit/theme presents itself as a design-token library (colors, spacing, radii, type and shadows over a vendored copy of Stitches, with a Tailwind preset). Its library code under dist/ is ordinary; the harm is in installing it. package.json declares a postinstall script, node scripts/setup.js, said to pre-compile dist/tokens.css with a native binary.

scripts/setup.js (lines 22 and 43-51) sets the download base to https://gitea.com/MichaelTrowel/brandkit/releases/download/v<version>, fetches runtime-<platform>-<arch>.gz over HTTPS following redirects (lines 53-87), then writes it to the temp directory as brandkit-<version>-runtime-<platform>, gunzips it, marks it executable and runs it with its output discarded (lines 94-105). No hash is pinned and no signature is checked.

The downloaded runtime-linux-x64 binary, identical for v2.4.1 and v2.4.2, is a stripped, statically linked Go executable (module brandkit/runtime, source file leaker.go). It decodes its configuration from hex and XOR with the key "BrKt2026", collects the hostname, the current time and the values of ANTHROPIC_API_KEY, GEMINI_API_KEY and AI_GATEWAY_KEY from the environment, and POSTs them as JSON (keys h, t, v0, v1, v2; User-Agent brandkit-runtime/1.0) to https://brandkit-9e7fae92.requestcatcher.com/activate, an inbox on a public request-recording service read by whoever created it.

The npm account gmeen published 0.0.0-stage (a placeholder with no install script) on 2026-11-15 at 22:24 UTC, 2.4.1 at 22:26 and 2.4.2 at 22:39; 2.4.1 and 2.4.2 carry the postinstall. The gitea repository serving the binary was created at 21:41 the same day. By 2026-11-16 02:00 UTC the npm registry no longer served the package; the binary was still downloadable from the gitea release.

Anyone who installed 2.4.1 or 2.4.2 should treat ANTHROPIC_API_KEY, GEMINI_API_KEY and AI_GATEWAY_KEY present in the installing environment as exposed and rotate them.

Malicious versions

2 flagged
2.4.12.4.2

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @brandkit/theme (2 malicious versions).

  2. If you installed it — respond

    Remove @brandkit/theme 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.

  3. Did it already run?

    If @brandkit/theme 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. @brandkit/theme on npm has been identified as a malicious package (versions 2.4.1, 2.4.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Bitbison · finder

Detect & block this

O3 blocks @brandkit/theme-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

@brandkit/theme (npm) malicious package — MAL-2026-20041 | O3 Security