@decocms/blocks-cli@7.49.0
Deco codegen (generate-blocks, generate-schema, generate-invoke) and Fresh-to-TanStack migration tooling
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe migration transfers a potentially privileged environment token to a package-selected project without a recipient-specific consent check. This is concrete credential disclosure and warrants blocking.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Running the migration outside dry-run mode while SUPABASE_ACCESS_TOKEN is set.
Impact
The token is disclosed to the selected project API, which the request also uses to modify central site metadata.
Mechanism
The package places the token in a bearer authorization header on a request to the hard-coded project endpoint.
Attack narrative
A normal migration run calls analytics provisioning unless dry-run is enabled. That code reads SUPABASE_ACCESS_TOKEN and sends it as a bearer credential to a hard-coded Deco Supabase project, where it submits a central site metadata update. The source does not establish recipient-specific consent for forwarding the environment credential.
AI rationale
The migration transfers a potentially privileged environment token to a package-selected project without a recipient-specific consent check. This is concrete credential disclosure and warrants blocking.
Evidence
scripts/migrate.ts
Network endpoints1
api.supabase.com/v1/projects/ozksgdmyrqcxcwhnbepg/database/query
Decision evidence
public snapshotAI called this Malicious at 96.0% confidence as Malware with low false-positive risk.
Evidence for block
- During a non-dry-run migration, scripts/migrate.ts calls analytics provisioning after bootstrap.
- Analytics provisioning reads SUPABASE_ACCESS_TOKEN from the environment and skips the request only when the variable is absent.
- The request sends that token as a bearer credential to the hard-coded central Deco Supabase project and submits a database update.
- The package manifest has no install lifecycle hook; the credential transfer is activated by the migration command.
Evidence against
- The transfer is conditional on SUPABASE_ACCESS_TOKEN being present and the migration running outside dry-run mode.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
5 flagged · loading sourcescripts/audit-observability-config.test.tsView file
309} {
L310: const { spawnSync } = require("node:child_process") as typeof import(
L311: "node:child_process"
High
Child Process
Package source references child process execution.
scripts/audit-observability-config.test.tsView on unpkg · L309scripts/sync-blocks-to-kv.tsView file
77purgeUrl: val("--purge-url", ""),
L78: purgeToken: val("--purge-token", process.env.PURGE_TOKEN ?? ""),
L79: };
...
L82: function gitChangedFiles(since: string, blocksDir: string): string[] {
L83: const out = execSync(`git diff --name-only ${since} HEAD`, { encoding: "utf-8" });
L84: return changedBlockFiles(out, blocksDir);
...
L87: async function purgeCache(origin: string, token: string, paths: string[]): Promise<void> {
L88: const res = await fetch(new URL("/_cache/purge", origin).toString(), {
L89: method: "POST",
High
Same File Env Network Execution
A single source file combines environment access, network access, and code or shell execution; review context before blocking.
scripts/sync-blocks-to-kv.tsView on unpkg · L77Findings
1 Critical5 High3 Medium5 Low
CriticalPrevious Version Dangerous Deltascripts/generate.ts
HighChild Processscripts/audit-observability-config.test.ts
HighShell
HighSame File Env Network Executionscripts/sync-blocks-to-kv.ts
HighRuntime Package Installscripts/generate-invoke.test.ts
HighSemantic Analysis Limitedscripts/audit-observability-config.ts#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @decocms/blocks-cli@7.49.0.
See all versions of @decocms/blocks-cli for other recorded verdicts.
- Avoid installing @decocms/blocks-cli@7.49.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.