registry / @wayai/cli / 0.3.199
@wayai/cli@0.3.199
WayAI CLI — sync hub configuration between local files and the platform
AI Security Review
scanned 25d ago · by lpm-firewall-aiStatic inspection supports a clean verdict: the scanner’s execution and decoding signals correspond to CLI update and JWT validation behavior, while the alleged credential redirection and obfuscated loader were not substantiated by inspected source. No npm install hook or confirmed attack surface was found.
Static reason
One or more suspicious static signals were detected.
Trigger
The package exposes the `wayai` command; the npm manifest defines no install lifecycle hook.
Impact
No confirmed credential theft, hidden code execution, or unconsented agent control-surface mutation was established.
Mechanism
Inspected network behavior was consistent with the WayAI API, decoding was used to validate a JWT header, and npm installation was tied to an explicit update command. The cited agent skill paths are consistent with the package’s harness integration.
AI rationale
Static inspection supports a clean verdict: the scanner’s execution and decoding signals correspond to CLI update and JWT validation behavior, while the alleged credential redirection and obfuscated loader were not substantiated by inspected source. No npm install hook or confirmed attack surface was found.
Evidence
package.jsondist/index.js
Network endpoints2
api.wayai.proraw.githubusercontent.com/wayai-pro/wayai-skill/main/skills/wayai/SKILL.md
Decision evidence
public snapshotAI called this Clean at 86.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes a CLI entrypoint and has no install lifecycle hook; its scripts are build, development, typecheck, and test commands.
- dist/index.js identifies the program as the `wayai` CLI and maps skills to the expected harness directories.
- The login module uses the package’s WayAI API endpoint; the inspected code did not establish forwarding of prompted credentials to an unrelated recipient.
- The reported base64 decoding is JWT header validation, not hidden payload execution.
- Runtime npm installation is inside an explicit update command.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
7 flaggeddist/index.jsView file
15042});
L15043: import { execFileSync } from "child_process";
L15044: import * as fs3 from "fs";
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
api_key: { type: "password", label: "Resend API Key", placeholder: "re_xxxxxxxxxx", description: "From resend.com/api-keys", required: true, maskInEdit: true, useExistingPlaceholde...
api_key: { type: "pa
High
Credential Redirect Persistence
Manifest-reachable source sends a prompted API credential to a fixed unofficial gateway and persists the redirection.
dist/index.jsView on unpkg51while (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, "..", "
Findings
7 High4 Medium4 Low
HighChild Processdist/index.js
HighShell
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.199.
See all versions of @wayai/cli for other recorded verdicts.
- Review the evidence and your use of @wayai/cli@0.3.199 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.