This report shows the evidence for @brandkit/theme@2.4.2. 2 of 2 known versions are blocked or flagged.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-20041 identifies this version as malicious and supplies the Firewall block. LPM AI assessed this version as suspicious; the assessments disagree.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-20041 confirms this npm version as malicious.
Advisory
MAL-2026-20041
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @brandkit/theme (npm)
Details
@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.
LPM's AI review found this version suspicious. That disagrees with the OpenSSF/OSV advisory, which supplies the block.
The install hook automatically downloads and runs native code that is not included for review. Its stated compiler role is plausible and related to the package, so the source does not establish malicious behavior, but the unverified install-time execution is a real risk.
Static reason
One or more suspicious static signals were detected.
Trigger
Package installation, through the postinstall script.
Impact
The binary can perform native code actions with the installer's privileges; its actual behavior is not established by the available source.
Mechanism
Downloads a versioned gzip asset from Gitea, decompresses it in the system temporary directory, then executes it.
The versions list below shows the verdict for each recorded version.
Avoid installing @brandkit/theme@2.4.2. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.