@flydocs/cli@1.3.11
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe credential source, unrestricted destination selection, and network send path are all present in the active CLI. There is no install lifecycle hook, so the concrete risk is conditional rather than automatic malware behavior.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Run a CLI command that uses the relay after setting FLYDOCS_RELAY_URL.
Impact
Conditional exposure of the FlyDocs API key and submitted project context to the selected endpoint.
Mechanism
Forwards a resolved API key to an unrestricted environment-selected endpoint.
AI rationale
The credential source, unrestricted destination selection, and network send path are all present in the active CLI. There is no install lifecycle hook, so the concrete risk is conditional rather than automatic malware behavior.
Evidence
dist/cli.js.flydocs/credentials.json~/.flydocs/credentials
Network endpoints2
app.flydocs.ai/api/relayFLYDOCS_RELAY_URL
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The CLI resolves a FlyDocs API key from project and global credential files.
- The relay destination is fully overridden by FLYDOCS_RELAY_URL, while requests attach the resolved API key as a Bearer credential.
- A relay request sends project context to the selected base URL with those credential headers.
Evidence against
- package.json has no preinstall, install, or postinstall lifecycle script.
- The flagged Claude hook is template code copied only during the user-invoked init flow.
- Claude OAuth plan-status requests target api.anthropic.com directly and are gated by plan-status consent.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
13 flaggeddist/cli.jsView file
•path = dist/cli.js
kind = trigger_reachable_excluded_payload
sizeBytes = 845128
triggerReachableSource = dist/cli.js
excludedPayload = template/.claude/hooks/auto-approve.py
Critical
Trigger Reachable Excluded Directory Payload
A package entrypoint or install-reachable source explicitly loads and activates an executable-looking payload from a test, fixture, or hidden path.
dist/cli.jsView on unpkg•matchType = previous_version_dangerous_delta
matchedPackage = @flydocs/cli@1.3.22
matchedIdentity = npm:QGZseWRvY3MvY2xp:1.3.22
similarity = 0.500
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/cli.jsView on unpkg130});
L131: import { spawnSync } from "child_process";
L132: import { readFile as readFile2, realpath } from "fs/promises";
High
Findings
2 Critical9 High5 Medium5 Low
CriticalTrigger Reachable Excluded Directory Payloaddist/cli.js
CriticalPrevious Version Dangerous Deltadist/cli.js
HighChild Processdist/cli.js
HighShelldist/cli.js
HighCredential Exfiltrationdist/cli.js
HighCredential Redirect Persistencedist/cli.js
HighCommand Output Exfiltrationdist/cli.js
HighSandbox Evasion Gated Capabilitydist/cli.js
HighTrigger Reachable Credential Exfiltrationdist/cli.js
HighRuntime Package Installdist/cli.js
HighPayload In Excluded Dirtemplate/.claude/hooks/repo_context.py
MediumDynamic Require
Affected versions and remediation
This report applies to @flydocs/cli@1.3.11.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.11 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.