registry / AI-agent control-surface risk / @inboost-dev/inboost-ai-proxy
@inboost-dev/inboost-ai-proxy
Local inference proxy and reliability gateway for Claude Code, Cursor, OpenHands, and Cline
This report shows the evidence for @inboost-dev/inboost-ai-proxy@0.3.0, the only known version.
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe automatic postinstall path writes behavior-bearing configuration into AI-agent control locations without consent. This is concrete install-time control-surface mutation and warrants blocking.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Installing the package through npm, which runs its postinstall hook.
Impact
Agent behavior can be influenced by configuration added during package installation.
Mechanism
The hook calls the installer, which writes into Claude Code configuration directories without a consent check.
Policy narrative
On npm installation, the package's postinstall hook invokes its agent skills installer. The installer writes package-provided skills and rules into global and project Claude Code configuration locations without an explicit user command or consent gate, creating an unconsented agent control surface.
AI rationale
The automatic postinstall path writes behavior-bearing configuration into AI-agent control locations without consent. This is concrete install-time control-surface mutation and warrants blocking.
Evidence
package.jsonbin/inboost-proxy.js~/.claude/skills/inboost-proxy/SKILL.md~/.claude/CLAUDE.md~/.claude/commands/inboost.md.claude/skills/inboost-proxy/SKILL.mdCLAUDE.md
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
- The package postinstall hook launches the CLI with the postinstall flag.
- That flag calls a handler that invokes the agent skills installer without a consent check.
- The installer writes files under global and project Claude Code configuration directories.
Evidence against
- The source describes the installed files as InBoost proxy skills and rules.
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-dev/inboost-ai-proxy@0.3.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @inboost-dev/inboost-ai-proxy@0.3.0. 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.