@codemarc/blt@1.10.16
blt cli
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe command sends Stripe or Square credentials to a hard-coded Supabase project whenever the user has not supplied a project ref. The explicit command invocation does not disclose or confirm that target, making this credential transfer malicious.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs `blt deploy secrets` with Supabase CLI authentication and payment credentials available.
Impact
Payment credentials may be stored in a Supabase project the user did not select, allowing its controller to access them.
Mechanism
The command reads Stripe or Square credentials from environment variables or the Trailz keys bundle. Unless `SUPABASE_PROJECT_REF` is set, it targets hard-coded project `erpofhdbqnvltzggpnrn` and submits the secrets through the Supabase CLI.
Attack narrative
When invoked, `blt deploy secrets` reads Stripe or Square credentials and sends them to Supabase. If the user has not set `SUPABASE_PROJECT_REF`, the command silently targets the hard-coded project `erpofhdbqnvltzggpnrn`, which the user did not choose through this command.
AI rationale
The command sends Stripe or Square credentials to a hard-coded Supabase project whenever the user has not supplied a project ref. The explicit command invocation does not disclose or confirm that target, making this credential transfer malicious.
Evidence
dist/commands/deploy.jsdist/commands/deploy/secrets.js.trailz/keys/keys.bin
Network endpoints1
supabase.com
Decision evidence
public snapshotAI called this Malicious at 95.0% confidence as Malware with low false-positive risk.
Evidence for block
- The `deploy secrets` command calls `setSecrets` and is described as setting Supabase secrets from environment variables or a workspace key bundle.
- `setSecrets` reads `STRIPE_SECRET_KEY` and `SQUARE_ACCESS_TOKEN` from the environment or Trailz key bundle.
- Without `SUPABASE_PROJECT_REF`, the command uses hard-coded project ref `erpofhdbqnvltzggpnrn` and passes the Stripe key to `bunx supabase secrets set` for that project.
Evidence against
- The transfer runs only when a user invokes `blt deploy secrets` and passes Supabase authentication checks.
- The manifest has no install hook; `prepublishOnly` builds the package.
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.16.
See all versions of @codemarc/blt for other recorded verdicts.
- Avoid installing @codemarc/blt@1.10.16. 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.