@codemarc/blt@1.10.15
blt cli
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe secrets command sends a Stripe credential to a hard-coded Supabase project unless the user overrides the project reference. That publisher-selected destination makes this credential exfiltration despite requiring an explicit command.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
The user runs `blt deploy secrets` without setting `SUPABASE_PROJECT_REF`.
Impact
A Stripe credential may be disclosed to a publisher-selected Supabase project.
Mechanism
The command reads `STRIPE_SECRET_KEY` from the environment or `.trailz/keys/keys.bin`, then invokes the Supabase CLI to set it on project `erpofhdbqnvltzggpnrn`.
Attack narrative
Running `blt deploy secrets` reads the Stripe secret from the environment or workspace key bundle. Unless the user overrides `SUPABASE_PROJECT_REF`, it targets the hard-coded project `erpofhdbqnvltzggpnrn` and passes the secret to `bunx supabase secrets set`. The command's documented purpose identifies Supabase secrets but does not disclose this default destination.
AI rationale
The secrets command sends a Stripe credential to a hard-coded Supabase project unless the user overrides the project reference. That publisher-selected destination makes this credential exfiltration despite requiring an explicit command.
Evidence
dist/commands/deploy/secrets.jsdist/commands/deploy.js.trailz/keys/keys.bin
Network endpoints1
supabase.com
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- The secrets command defaults to the hard-coded Supabase project ref `erpofhdbqnvltzggpnrn`.
- It reads `STRIPE_SECRET_KEY` from the environment or the workspace key bundle.
- It passes that Stripe key to `bunx supabase secrets set` with the selected project ref.
- The secrets-setting function is called by the `blt deploy secrets` command.
Evidence against
- The transfer requires a user to run the secrets deployment command.
- The DigitalOcean helper sends DigitalOcean tokens to DigitalOcean's official API for its stated API operations.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
4 flaggeddist/lib/github.jsView file
1import { spawnSync } from "node:child_process";
L2: export function ensureGhInstalled(logger) {
High
dist/lib/digitalocean.jsView file
4import { homedir } from "node:os";
L5: const DO_API = "https://api.digitalocean.com/v2";
L6: function readDoctlToken() {
L7: const configPath = process.platform === "darwin"
L8: ? join(homedir(), "Library", "Application Support", "doctl", "config.yaml")
L9: : join(homedir(), ".config", "doctl", "config.yaml");
...
L19: function getToken() {
L20: const token = process.env.DIGITALOCEAN_ACCESS_TOKEN ??
L21: process.env.DIGITALOCEAN_TOKEN ??
...
L39: return undefined;
L40: const body = await res.text();
L41: if (!res.ok) {
High
Sandbox Evasion Gated Capability
Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/lib/digitalocean.jsView on unpkg · L4Findings
1 Critical4 High3 Medium5 Low
CriticalPrevious Version Dangerous Deltadist/commands/version/update.js
HighChild Processdist/lib/github.js
HighShell
HighSandbox Evasion Gated Capabilitydist/lib/digitalocean.js
HighRuntime Package Installdist/commands/deploy/functions.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @codemarc/blt@1.10.15.
See all versions of @codemarc/blt for other recorded verdicts.
- Avoid installing @codemarc/blt@1.10.15. 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.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.