registry / Credential exfiltration / @codemarc/blt
@codemarc/blt
blt cli
This report shows the evidence for @codemarc/blt@1.11.0. 4 of 9 known versions are blocked or flagged. The newest version, 1.11.1, is allowed. See all versions.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe explicit secrets command sends a locally found Stripe credential to a hard-coded Supabase project whenever the user has not supplied a project ref. That undisclosed default destination makes this 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
The Stripe secret is exposed to the owner or operators of the selected Supabase project and could be used to access the associated Stripe account.
Mechanism
The command reads `STRIPE_SECRET_KEY` from the environment or keys bundle, then invokes Supabase CLI to store it under the package’s fixed project ref.
Attack narrative
When a user runs `blt deploy secrets` without a project override, the command retrieves a Stripe secret from the environment or `.trailz/keys/keys.bin` and passes it to Supabase CLI with the package’s hard-coded project ref. This sends the credential to a project the package selected, rather than one the user explicitly configured.
AI rationale
The explicit secrets command sends a locally found Stripe credential to a hard-coded Supabase project whenever the user has not supplied a project ref. That undisclosed default destination makes this credential exfiltration.
Evidence
dist/commands/deploy/secrets.jsdist/commands/deploy.js.trailz/keys/keys.bin
Decision evidence
public snapshotAI called this Malicious at 93.0% confidence as Malware with low false-positive risk.
Evidence for block
- `deploy secrets` reads payment credentials from environment variables or the `.trailz/keys/keys.bin` bundle.
- When `SUPABASE_PROJECT_REF` is unset, the code selects the package’s hard-coded project ref `erpofhdbqnvltzggpnrn`.
- The command passes the Stripe secret to `bunx supabase secrets set` for that selected project.
- This transfer is triggered by the explicit `blt deploy secrets` command.
Evidence against
- The command is documented in its CLI help as setting Supabase secrets from environment variables or the keys bundle.
- Users can override the default project by setting `SUPABASE_PROJECT_REF`.
- DigitalOcean credentials are sent to the DigitalOcean API for the package’s droplet and DNS 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/device/launcher.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.11.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @codemarc/blt@1.11.0. 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.