registry / @wayai/cli / 0.3.160
@wayai/cli@0.3.160
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete malware or install-hook abuse was found, but the package has an unresolved AI-agent extension lifecycle risk through automatic symlinking and remote skill installation. The privileged file-write path is user-invoked and authenticated, so it warrants a warning rather than a block.
Static reason
One or more suspicious static signals were detected.
Trigger
Run a non-help wayai command in a repository containing .agents/skills/wayai, or explicitly run wayai admin skill install.
Impact
A linked or installed skill may be loaded by an AI harness; remote skill content is not bundled for static verification.
Mechanism
AI harness skill linking and authenticated remote skill installation.
AI rationale
No concrete malware or install-hook abuse was found, but the package has an unresolved AI-agent extension lifecycle risk through automatic symlinking and remote skill installation. The privileged file-write path is user-invoked and authenticated, so it warrants a warning rather than a block.
Evidence
dist/index.js.agents/skills/wayai/SKILL.md.claude/skills/wayai.claude/skills/wayai-admin.opencode/skills/wayai-admin.agents/skills/wayai-admin
Network endpoints1
api.wayai.pro
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Dangerous Capability with low false-positive risk.
Evidence for warning
- On ordinary non-help CLI commands, the program creates a Claude skill symlink when a WayAI skill exists under .agents.
- The explicit admin skill install command fetches server-provided files and writes them into every detected AI harness skill directory.
- The CLI includes a user-invoked global self-update command that runs npm install.
Evidence against
- package.json has no preinstall, install, postinstall, or other lifecycle hook.
- The agent-skill file write is behind an explicit admin command and requires authentication.
- The automatic network refresh only reads version metadata and caches it; it does not execute fetched content.
- No credential harvesting, secret exfiltration, install-time execution, or runtime self-dependency was found.
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
Source & flagged code
5 flaggeddist/index.jsView file
14704});
L14705: import { execFileSync } from "child_process";
L14706: import * as fs2 from "fs";
High
51while (cursor < text.length) {
L52: while (cursor < text.length && !isBase64UrlChar(text[cursor])) cursor++;
L53: const headerStart = cursor;
...
L236: "use strict";
L237: CREDENTIAL_KEY_RE = /token|secret|credential|password|passwd|api[_-]?key|authorization|private[_-]?key|session[_-]?id|cookie|jwt/i;
L238: NUMERIC_CREDENTIAL_KEY_RE = /(?:password|passwd|pin|token|secret|credential|api[_-]?key|authorization|private[_-]?key|session[_-]?id|cookie|jwt)$/i;
...
L249: [/\bway_[A-Za-z0-9_-]{8,}/g, "way_[REDACTED]"],
L250: // wst_ single-use WebSocket tickets (same opaque base64url format).
L251: [/\bwst_[A-Za-z0-9_-]{8,}/g, "wst_[REDACTED]"],
...
L366: try {
L367: const __dirname2 = dirname(fileURLToPath(import.meta.url));
L368: const pkg2 = JSON.parse(readFileSync(join(__dirname2, "..", "
High
Sandbox Evasion Gated Capability
Source gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
dist/index.jsView on unpkg · L5116086package = @wayai/cli; repositoryIdentity = platform; dependency = @napi-rs/keyring
L16086: try {
L16087: const mod = await import("@napi-rs/keyring");
L16088: const Entry = mod.Entry;
Findings
5 High3 Medium5 Low
HighChild Processdist/index.js
HighShell
HighSandbox Evasion Gated Capabilitydist/index.js
HighCopied Package Dependency Bridgedist/index.js
HighRuntime Package Installdist/index.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowEvaldist/index.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @wayai/cli@0.3.160.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.160 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.