registry / @wirecat/max-cli / 0.64.0
@wirecat/max-cli@0.64.0
MAX Messenger bots through the official Bot API, and a personal MAX account, from the terminal — built for agents and scripts
AI Security Review
scanned 17d ago · by lpm-firewall-aiInspected the lifecycle hook, CLI entrypoint, browser token flow, bot transport, downloader, and Windows helper. The reviewed behavior is gated or aligned with MAX login and API use, with no confirmed attack identified.
Static reason
One or more suspicious static signals were detected.
Trigger
A global npm installation may invoke postinstall; browser token retrieval occurs when the user starts browser login.
Impact
No confirmed attack surface was established in the inspected source.
Mechanism
Postinstall gates setup on global installation and requires an agent selection to install an agent skill. Browser login retrieves a token from the MAX web client and removes its temporary profile; bot requests send the supplied token to the MAX Bot API.
AI rationale
Inspected the lifecycle hook, CLI entrypoint, browser token flow, bot transport, downloader, and Windows helper. The reviewed behavior is gated or aligned with MAX login and API use, with no confirmed attack identified.
Evidence
install/postinstall.mjsdist/install/postinstall.jsdist/session/browser.jsdist/bot/transport.js
Network endpoints2
web.max.ru/platform-api2.max.ru
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The postinstall hook runs its setup only for global npm installs; agent skill installation requires an explicit agent setting, and `prepare` only runs `lefthook install`.
- Browser login opens the MAX web client in a temporary profile, reads its stored token from that client, and removes the profile when done.
- The bot transport uses the MAX Bot API endpoint and sends the caller-provided token to that API.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
5 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
3 High5 Medium5 Low
HighInstall Time Lifecycle Scriptspackage.json
HighSandbox Evasion Gated Capabilitydist/session/browser.js
HighSemantic Analysis Limiteddist/bot/transport.js#virtual:normalized:round1
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.64.0.
See all versions of @wirecat/max-cli for other recorded verdicts.
- Review the evidence and your use of @wirecat/max-cli@0.64.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.