@wayai/cli@0.3.285
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 2h ago · by lpm-firewall-aiThe flagged OpenAI credential flow belongs to user-requested TTS and sends the key to OpenAI. However, the installed CLI silently enables Sentry error reporting by default, so this is suspicious runtime telemetry rather than a clean result.
Static reason
One or more suspicious static signals were detected.
Trigger
An installed CLI runs and a foreground command throws an error that passes the Sentry reporting filter.
Impact
Exception details and limited command and runtime metadata leave the local process; the source masks secrets in messages and scrubs the home directory from stack paths.
Mechanism
The CLI initializes Sentry with a fixed DSN and captures the exception. Telemetry can be disabled with WAYAI_TELEMETRY_DISABLED=1.
AI rationale
The flagged OpenAI credential flow belongs to user-requested TTS and sends the key to OpenAI. However, the installed CLI silently enables Sentry error reporting by default, so this is suspicious runtime telemetry rather than a clean result.
Evidence
dist/index.js
Network endpoints1
o4510669417807872.ingest.us.sentry.io
Decision evidence
public snapshotAI called this Suspicious at 91.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- Installed CLI runs initialize Sentry by default; `WAYAI_TELEMETRY_DISABLED=1` disables it.
- Foreground command errors that pass the reporting filter are automatically sent with `captureException`.
- Sentry is configured with a fixed `o4510669417807872.ingest.us.sentry.io` endpoint and tags for the command, Node version, OS platform, and architecture.
Evidence against
- The OpenAI API key is used by the explicitly requested TTS feature and sent to `api.openai.com`.
- The Sentry hook masks secrets in error messages and scrubs the home directory from stack paths.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
8 flaggeddist/index.jsView file
16816});
L16817: import { execFileSync } from "child_process";
L16818: import * as fs3 from "fs";
High
9118"type": "string",
L9119: "description": "The Bash script to run, as with `bash -c`. It runs in /workspace unless it changes directory."
L9120: },
High
•Manifest-reachable source captures an API credential, sends it to a fixed unofficial gateway, and persists that redirection in agent or shell configuration.
dist/index.js:
CREDENTIAL_KEY_RE = /token|secret|credential|password|passwd|api[_-]?key|authorization|private[_-]?key|session[_-]?id|cookie|jwt/i;
NUMERIC_CREDENTIAL_KEY_RE = /(?:password|passwd|pin|token|secret|credential|api[_-]?key|authorization|private[_-]?key|session[_-]?id|cookie|jwt)$/i;
// Stripe API keys and webhook signing secrets. Keep this aligned with
// LLM provider API keys. The captured delimiter is deliberate: `_` may
function writeFileNoFollow(root, abs, data) {
fs.writeFileSync(abs, data);
function writeFileIfChangedNoFollow(root, abs, content) {
if (!writeFileNoFollow(root, abs, bytes)) throw symlinkRefusal(path.rel
Findings
7 High4 Medium4 Low
HighChild Processdist/index.js
HighShelldist/index.js
HighCredential Redirect Persistencedist/index.js
HighSandbox Evasion Gated Capabilitydist/index.js
HighObfuscated Payload Loaderdist/index.js
HighCopied Package Dependency Bridgedist/index.js
HighRuntime Package Installdist/index.js
MediumDynamic Requiredist/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @wayai/cli@0.3.285.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.285 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.