inboost-ai-proxy@0.3.3
Local inference proxy and reliability gateway for Claude Code, Cursor, OpenHands, and Cline
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe verified postinstall hook makes unconsented changes to global and project AI assistant control files across multiple tools. This meets the policy for blocking lifecycle mutation of a broad agent control surface.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm installation runs the postinstall hook.
Impact
Future assistant sessions can follow package-installed rules and route requests through the configured local proxy.
Mechanism
The hook installs skills and appends or writes assistant configuration across Claude Code, Cursor, OpenHands, and other tools without an affirmative consent check.
Policy narrative
The package’s postinstall hook invokes its skills installer automatically. That installer writes global assistant configuration and appends rules to existing configuration across several tools, without a consent check. The added rules direct assistant behavior and set Claude Code to use the local proxy.
AI rationale
The verified postinstall hook makes unconsented changes to global and project AI assistant control files across multiple tools. This meets the policy for blocking lifecycle mutation of a broad agent control surface.
Evidence
package.jsonbin/inboost-proxy.js
Network endpoints1
localhost:8080
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 97.0% confidence with low false-positive risk.
Evidence for policy risk
- package.json runs bin/inboost-proxy.js --postinstall during installation.
- The postinstall handler calls installIDESkills without asking for confirmation.
- The installer writes global Claude and Cursor settings and also changes project and other agent settings.
- Its write helper creates directories and writes files; the installer also appends rules to existing settings.
- The installed skill tells coding assistants to follow its rules and route Claude Code requests through the local proxy.
Evidence against
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
10 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node bin/inboost-proxy.js --postinstall
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node bin/inboost-proxy.js --postinstall
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgbin/inboost-proxy.jsView file
15L16: const { spawn, spawnSync } = require("child_process");
L17: const path = require("path");
...
L19: const os = require("os");
L20: const http = require("http");
L21: const https = require("https");
...
L200: function installIDESkills(verbose = true) {
L201: const homeDir = os.homedir();
L202: const cwd = process.cwd();
...
L299: try {
L300: const isWindows = process.platform === "win32";
L301: const cmd = isWindows ? "where" : "which";
Critical
Findings
3 Critical5 High5 Medium4 Low
CriticalDownload Executebin/inboost-proxy.js
CriticalAi Agent Control Hijackbin/inboost-proxy.js
CriticalTrigger Reachable Dangerous Capabilitybin/inboost-proxy.js
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processbin/inboost-proxy.js
HighSandbox Evasion Gated Capabilitybin/inboost-proxy.js
HighTrigger Reachable External Ai Agent Control Surface Mutationbin/inboost-proxy.js
HighTrigger Reachable Persistencebin/inboost-proxy.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencebin/inboost-proxy.js
Affected versions and remediation
This report applies to inboost-ai-proxy@0.3.3.
See all versions of inboost-ai-proxy for other recorded verdicts.
- Avoid installing inboost-ai-proxy@0.3.3. 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.