registry / @wirecat/max-cli / 0.78.0
@wirecat/max-cli@0.78.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 6d ago · by lpm-firewall-aiThe package adds a root CA intended for the MAX Bot API, but Node’s implementation changes trust for every later TLS connection in the process. This is a meaningful trust expansion beyond the package’s own requests, so it warrants a warning; the source does not show credential theft or unrelated network use.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Construction of BotTransport when no custom fetch implementation is supplied, on Node versions supporting setDefaultCACertificates.
Impact
A certificate chaining to this root could be accepted by other TLS clients in the same process, extending trust beyond MAX API requests.
Mechanism
botFetch appends the package-shipped root certificate to Node’s process-wide default CA certificates; later TLS connections in that process trust it too.
AI rationale
The package adds a root CA intended for the MAX Bot API, but Node’s implementation changes trust for every later TLS connection in the process. This is a meaningful trust expansion beyond the package’s own requests, so it warrants a warning; the source does not show credential theft or unrelated network use.
Evidence
dist/bot/transport.jsdist/bot/russian-trusted-root.js
Network endpoints2
platform-api2.max.ruweb.max.ru
Decision evidence
public snapshotAI called this Suspicious at 89.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- When Node supports setDefaultCACertificates, botFetch adds the Russian Trusted Root CA to the process-wide default, so all later TLS connections in that process trust it.
- BotTransport uses botFetch by default when constructed, making the trust change occur when bot transport is initialized.
- The certificate source says the root signs platform-api2.max.ru and is intended for the package’s own bot requests, but the implementation applies it process-wide.
Evidence against
- The install hook exits unless npm_config_global is true; it does not run its setup for ordinary local installs.
- The added certificate is described as being for the official MAX Bot API endpoint, and the package documents the broader Node trust effect in source.
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.78.0.
See all versions of @wirecat/max-cli for other recorded verdicts.
- Review the evidence and your use of @wirecat/max-cli@0.78.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.