@brandkit/theme npm postinstall steals AI API keys via downloaded Go binary
Severity: critical · Patch status: no-fix-needed · Since 2026-11-17
The npm package @brandkit/theme, posing as a design-token library, shipped a postinstall script (scripts/setup.js) in versions 2.4.1 and 2.42 that downloaded a gzipped Go binary from a gitea.com release, executed it with no hash or signature verification. The binary (leaker.go) XOR-decodes its config with key "BrKt2026", collects hostname, time and the ANTHROPICAPIKEY, GEMINIAPIKEY and AIGATEWAYKEY environment variables, and POSTs them to a public requestcatcher.com inbox. Publisher account gmeen uploaded the versions on 2026-11-15; npm removed the package by 2026-11-16 02:00 UTC, though the binary remained downloadable. Anyone who installed 2.4.1 or 2.4.2 must treat those AI keys as compromised. No patched versions exist; the package is removed.
What to do
- If @brandkit/theme 2.4.1 or 2.4.2 was installed, immediately rotate ANTHROPIC_API_KEY, GEMINI_API_KEY and AI_GATEWAY_KEY exposed in the installing environment
- Audit CI/CD and developer machines that ran the install for the downloaded brandkit runtime binary and any residual artifacts
- Check requestcatcher inbox access logs/exposure assumptions and review for unauthorized use of the exfiltrated keys
- Remove the package from lockfiles and block it in dependency firewalls; scan repositories for its dependency
Sources
All live incidents on Threat Watch