registry / AI-agent control-surface risk / inboost-proxy
inboost-proxy
Local inference proxy and reliability gateway for Claude Code, Cursor, OpenHands, and Cline (alias package)
This report shows the evidence for inboost-proxy@0.3.3. 3 of 3 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest-triggered postinstall mutates user-wide and project-wide coding-agent configuration without a consent prompt. The source confirms automatic control-surface changes, supporting a block under the install-time agent-control policy.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Installing the package through npm runs its postinstall hook.
Impact
Coding assistants can load unrequested instructions that direct their behavior and proxy configuration.
Mechanism
The hook calls an installer that writes skills and rules to agent configuration locations, including the user-wide Claude configuration.
Policy narrative
Installing the package automatically writes its skills and rules into coding-agent configuration, including user-wide locations. The embedded instructions direct assistant behavior and local proxy use, creating an unconsented agent control surface during package installation.
AI rationale
The manifest-triggered postinstall mutates user-wide and project-wide coding-agent configuration without a consent prompt. The source confirms automatic control-surface changes, supporting a block under the install-time agent-control policy.
Evidence
package.jsonbin/inboost-proxy.js
Decision evidence
public snapshotAI identified this as a dangerous AI-agent capability at 92.0% confidence with low false-positive risk.
Evidence for policy risk
- The npm postinstall hook automatically runs the package CLI with its postinstall flag.
- That handler calls the agent-skill installer without asking for consent.
- The installer writes a user-wide Claude skill and appends rules to the user-wide Claude configuration.
- It also installs integration files in user-wide agent configuration locations.
- The installed instructions require coding assistants to follow package-defined rules, including routing 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
Download Execute
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-proxy@0.3.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing inboost-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.