claude-multiacc
Unified Claude Code and OpenAI Codex subscription pooling with quota-aware selection.
This report shows the evidence for claude-multiacc@2.0.32. 20 of 61 known versions are blocked or flagged. The newest version, 2.0.61, is allowed. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is an unconsented postinstall mutation of a broad AI-agent control surface: it shadows Claude and Codex commands, persists scheduled jobs, and self-updates. The global-install guard does not remove the automatic lifecycle behavior or its control over later command execution.
Decision evidence
public snapshot- The package runs a postinstall hook that automatically starts its installer during global npm installation.
- The installer rewrites shell startup files so its bin directory precedes the existing PATH.
- It replaces the commands named claude and codex with package shims, including system-wide symlinks when run as root.
- It creates recurring launchd or cron jobs, including a daily job that installs the latest package release.
- The Codex shim intercepts normal codex invocations and executes the real binary only after applying its account-pool behavior.
- The postinstall hook skips local installs, CI, Windows, and an explicit opt-out environment setting.
- No hard-coded third-party exfiltration endpoint was found in the inspected installation path.
Source & flagged code
7 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to claude-multiacc@2.0.32.
The versions list below shows the verdict for each recorded version.
- Avoid installing claude-multiacc@2.0.32. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.