registry / @flydocs/cli / 1.3.21
@flydocs/cli@1.3.21
FlyDocs AI CLI — install, setup, and manage FlyDocs projects
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is not an install-time malware chain, but explicit setup modifies a project AI-agent control surface and enables background reporting from local AI session stores. The consent checks reduce risk but do not remove the need to warn users before deployment.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs FlyDocs initialization, then Claude Code reaches a Stop event in that project.
Impact
AI-session identifiers, token counts, model names, timestamps, repository slugs, and optionally enabled usage metadata can be sent to FlyDocs.
Mechanism
Project Claude hook launches a detached usage-report process.
AI rationale
This is not an install-time malware chain, but explicit setup modifies a project AI-agent control surface and enables background reporting from local AI session stores. The consent checks reduce risk but do not remove the need to warn users before deployment.
Evidence
dist/cli.jstemplate/.claude/settings.jsontemplate/.claude/hooks/usage-capture.py.claude/hooks.claude/settings.json~/.claude/projects~/.codex/sessions~/.cursor/ai-tracking/ai-code-tracking.db
Network endpoints1
app.flydocs.ai/api/relay/usage/sessions
Decision evidence
public snapshotAI called this Suspicious at 90.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- The explicit init command installs Claude hook files and merges project Claude settings.
- The installed Stop hook launches a detached usage-report command after each agent response.
- The CLI reads Claude, Codex, and Cursor local session data and posts selected usage metadata to FlyDocs.
- Usage reporting is gated by an API key, workspace consent state, and local opt-out checks.
Evidence against
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The wire record construction sends usage metadata and timestamps, not transcript message text.
- The template hook is deployed by an explicit CLI setup action, not automatically on npm installation.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
13 flaggeddist/cli.jsView file
•path = dist/cli.js
kind = trigger_reachable_excluded_payload
sizeBytes = 951444
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.16
matchedIdentity = npm:QGZseWRvY3MvY2xp:1.3.16
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 unpkg131});
L132: import { spawnSync } from "child_process";
L133: 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.21.
See all versions of @flydocs/cli for other recorded verdicts.
- Review the evidence and your use of @flydocs/cli@1.3.21 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.