registry / @wayai/cli / 0.3.238
@wayai/cli@0.3.238
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 15d ago · by lpm-firewall-aiSource inspection found no automatic install behavior or hidden payload execution. Credential use follows the CLI login flow, and the package installation command is confined to an explicit update command.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the CLI; package installation has no lifecycle hook, and updating requires invoking the update command.
Impact
No confirmed malicious impact was found; observed effects are CLI authentication, error reporting, and user-invoked updating.
Mechanism
Login validates a prompted token with the selected API before storing it in the OS keyring. The package install command is called by the explicit update function.
AI rationale
Source inspection found no automatic install behavior or hidden payload execution. Credential use follows the CLI login flow, and the package installation command is confined to an explicit update command.
Network endpoints2
api.wayai.prosprightly-comic-51.authkit.app
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI bundle and lists build and development scripts without an install, preinstall, or postinstall hook.
- Login validates the prompted WayAI token against the selected API before saving it; the default API is WayAI, and the update install command runs inside the update command.
- The cited dependency entrypoints and modules are JSON schema validation, native keyring loading, and Sentry/OpenTelemetry instrumentation.
Evidence against
- The bundle includes network and child-process operations, but inspected call paths tie them to WayAI API access, local keyring use, and the explicit update command.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
8 flaggeddist/index.jsView file
15494});
L15495: import { execFileSync } from "child_process";
L15496: import * as fs3 from "fs";
High
8772"type": "string",
L8773: "description": "The Bash script to run, as with `bash -c`. It runs in /workspace unless it changes directory."
L8774: },
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.238.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.238 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.