@codemarc/blt@1.10.13
blt cli
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe explicit secrets-deployment command sends Stripe and Square credentials to a hard-coded Supabase project when the user has not configured a project reference. Because that destination is publisher-selected and the transfer includes credentials for another service, this is credential exfiltration.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs `blt deploy secrets` without setting `SUPABASE_PROJECT_REF`.
Impact
Payment provider credentials can be exposed to a Supabase project chosen by the package publisher.
Mechanism
The command reads Stripe and Square secrets from environment variables or `.trailz/keys/keys.bin`, defaults to project ref `erpofhdbqnvltzggpnrn`, and invokes the Supabase CLI to set those secrets there.
Attack narrative
When a user runs `blt deploy secrets` without configuring `SUPABASE_PROJECT_REF`, the command sends available Stripe and Square credentials to the hard-coded Supabase project `erpofhdbqnvltzggpnrn`. This exposes payment credentials to a destination chosen by the publisher.
AI rationale
The explicit secrets-deployment command sends Stripe and Square credentials to a hard-coded Supabase project when the user has not configured a project reference. Because that destination is publisher-selected and the transfer includes credentials for another service, this is credential exfiltration.
Evidence
dist/commands/deploy.jsdist/commands/deploy/secrets.jsdist/commands/notify/keys.js.trailz/keys/keys.bin
Network endpoints2
Supabase service, project ref erpofhdbqnvltzggpnrn (via `bunx supabase`)supabase.com
Decision evidence
public snapshotAI called this Malicious at 98.0% confidence as Malware with low false-positive risk.
Evidence for block
- The documented `blt deploy secrets` command calls `setSecrets` when the user runs it.
- The command reads `STRIPE_SECRET_KEY` and `SQUARE_ACCESS_TOKEN` from the environment or the workspace keys bundle.
- If `SUPABASE_PROJECT_REF` is unset, the code selects the hard-coded project `erpofhdbqnvltzggpnrn`.
- It passes the Stripe secret to `bunx supabase secrets set` for that project.
Evidence against
- The credential transfer requires the user to run the explicit `deploy secrets` command.
- The package has no preinstall, install, or postinstall script.
- The DigitalOcean helper sends its token to the DigitalOcean API, matching its stated function.
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.13.
See all versions of @codemarc/blt for other recorded verdicts.
- Avoid installing @codemarc/blt@1.10.13. 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.