registry / @wirecat/max-cli / 0.70.0
@wirecat/max-cli@0.70.0
⚠ Under reviewMAX Messenger bots through the official Bot API, and a personal MAX account, from the terminal — built for agents and scripts
AI Security Review
scanned 12d ago · by lpm-firewall-aiInspected source behavior appears package-aligned and gated. The required clean citation set exceeds the 256-citation limit, so this review cannot certify a clean verdict.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Installation runs the declared postinstall hook; browser token reading follows a user-invoked login command.
Impact
No unintended recipient, destructive effect, or unconsented agent configuration change was established.
Mechanism
The hook is limited to global installs and only writes the package's own agent skill when an agent setting is supplied. Browser login reads a token from the MAX web client in a temporary profile.
AI rationale
Inspected source behavior appears package-aligned and gated. The required clean citation set exceeds the 256-citation limit, so this review cannot certify a clean verdict.
Decision evidence
public snapshotAI called this Manual Review at 72.0% confidence as Unknown with low false-positive risk.
AI review observations
- The manifest connects postinstall to a script that runs only for global npm installs.
- Agent skill installation requires an explicit agent setting and writes the package's own skill file to the selected agent directory.
- The browser login flow targets the MAX web client and reads its stored token during that login.
Evidence against
- The inspected install hook does not install an agent skill when the agent setting is absent or set to none.
- The browser login uses a temporary profile and closes it after the login attempt.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
6 flaggedpackage.jsonView file
•scripts.postinstall = node install/postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node install/postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/session/browser.jsView file
1import { spawn } from "node:child_process";
L2: import { existsSync, mkdtempSync, realpathSync, rmSync } from "node:fs";
...
L9: };
L10: const WEB_MAX = "https://web.max.ru/";
L11: const AUTH_KEY = "__oneme_auth";
...
L17: export const findChromium = () => {
L18: const named = process.env.MAX_BROWSER;
L19: if (named)
L20: return named;
L21: if (process.platform === "darwin") {
L22: return [
...
L129: // Chrome writes to the profile while it shuts down; removing it first leaves half of it behind.
Findings
4 High5 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSandbox Evasion Gated Capabilitydist/session/browser.js
HighSemantic Analysis Limiteddist/bot/transport.js#virtual:normalized:round1
HighPrevious Version Dangerous Deltadist/client/values.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperinstall/windows.ps1
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @wirecat/max-cli@0.70.0.
See all versions of @wirecat/max-cli for other recorded verdicts.
- Review the evidence and your use of @wirecat/max-cli@0.70.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.