registry / @wirecat/max-cli / 0.72.0
@wirecat/max-cli@0.72.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 11d ago · by lpm-firewall-aiInspected source shows guarded global-install setup and a MAX web login flow, with no concrete attack established. The required clean review covers 269 distinct paths, exceeding the 256-citation limit, so the package cannot be marked clean under this review’s citation requirements.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A global npm installation runs the postinstall wrapper; a selected agent target enables skill installation.
Impact
No attack impact was established in the inspected source.
Mechanism
The hook gates setup on global-install status and an agent-selection environment variable; the browser login code reads a token from the MAX web client’s local storage.
AI rationale
Inspected source shows guarded global-install setup and a MAX web login flow, with no concrete attack established. The required clean review covers 269 distinct paths, exceeding the 256-citation limit, so the package cannot be marked clean under this review’s citation requirements.
Decision evidence
public snapshotAI called this Manual Review at 97.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json defines a postinstall hook and a prepare hook that installs a project Git hook.
- The postinstall wrapper runs its setup only for global npm installs.
- The setup writes the bundled agent skill only when MAX_INSTALL_AGENT or TG_INSTALL_AGENT selects a target.
- The browser login code uses a temporary profile, reads the MAX web client’s stored login token, and removes the profile when it exits.
Evidence against
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.72.0.
See all versions of @wirecat/max-cli for other recorded verdicts.
- Review the evidence and your use of @wirecat/max-cli@0.72.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.