@trycodev/cli@0.12.0
Secure CoDev cloud coding-agent authentication CLI
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe CLI forwards provider authentication data to CoDev during explicit provider-auth commands. This matches the package's stated authentication purpose, but the source does not show a distinct consent step for sharing those provider credentials, so warn rather than block.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
A user runs the corresponding codev provider-auth command.
Impact
CoDev receives credentials that may let it act through the user's provider account. The flow is tied to explicit auth commands, but the source shows no separate confirmation specifically for forwarding the provider credentials.
Mechanism
The CLI reads provider auth data or extracts an OAuth token, then sends it to CoDev using the user's CoDev authentication.
AI rationale
The CLI forwards provider authentication data to CoDev during explicit provider-auth commands. This matches the package's stated authentication purpose, but the source does not show a distinct consent step for sharing those provider credentials, so warn rather than block.
Evidence
src/client.mjsbin/codev.mjs$TMPDIR/codev-codex-auth-*/auth.json$TMPDIR/codev-cursor-auth-*
Network endpoints3
www.trycodev.com/api/cli/codex-authwww.trycodev.com/api/cli/claude-authwww.trycodev.com/api/cli/cursor-auth
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The Codex auth flow reads auth.json and POSTs its contents to CoDev's /api/cli/codex-auth endpoint.
- The Claude auth flow POSTs the extracted OAuth token to CoDev's /api/cli/claude-auth endpoint.
- These transfers are triggered by explicit codev codex-auth and codev claude-auth commands.
- The CLI describes these as authentication flows using the official provider CLIs.
Evidence against
- The manifest has no install, preinstall, or postinstall hook.
- The package is described as a CoDev coding-agent authentication CLI, and the credential transfers occur in its named auth commands.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
10 flaggedsrc/mirror-upload.mjsView file
1import { execFile } from "node:child_process";
L2: import { createHash } from "node:crypto";
High
Child Process
Package source references child process execution.
src/mirror-upload.mjsView on unpkg · L1•matchType = normalized_sha256
matchedPackage = @trycodev/cli@0.10.0
matchedPath = src/mirror-upload.mjs
matchedIdentity = npm:QHRyeWNvZGV2L2NsaQ:0.10.0
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
src/mirror-upload.mjsView on unpkgsrc/share-files.mjsView file
1import { execFile } from "node:child_process";
L2: import { createHash } from "node:crypto";
...
L46: { maxBuffer: 64 << 20, encoding: "buffer" },
L47: (error, stdout) => resolve(error ? null : stdout),
L48: );
...
L57: if (!out) return null;
L58: return [...new Set(out.toString("utf8").split("\0").filter(Boolean))];
L59: }
Findings
1 Critical8 High3 Medium6 Low
CriticalHardcoded Runtime Data Exfiltrationsrc/client.mjs
HighChild Processsrc/mirror-upload.mjs
HighSame File Env Network Executionsrc/client.mjs
HighKnown Malware Source Similaritysrc/client.mjs
HighKnown Malware Source Similaritysrc/mirror-upload.mjs
HighKnown Malware Source Similaritysrc/clone.mjs
HighKnown Malware Source Similaritysrc/setup-codex.mjs
HighKnown Malware Source Similaritysrc/share-git.mjs
HighPrevious Version Dangerous Deltasrc/coordinate-git.mjs
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
Affected versions and remediation
This report applies to @trycodev/cli@0.12.0.
See all versions of @trycodev/cli for other recorded verdicts.
- Review the evidence and your use of @trycodev/cli@0.12.0 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.