@akashpandey/agent-relay@1.0.2
Pass the baton between Claude Code, Codex, Antigravity, and OpenCode with a single Unix command.
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe postinstall hook invokes an installer that deletes existing skill directories across several agent configuration locations and replaces them with package-controlled links. This is concrete unconsented install-time agent control-surface mutation.
Static reason
One or more suspicious static signals were detected.
Trigger
A global npm install or a direct install into the package directory.
Impact
Existing skill contents at those locations can be deleted and replaced, changing agent behavior.
Mechanism
The hook runs the installer, which removes existing non-symlink skill directories in several agent configuration locations and creates symlinks to the package skill.
Policy narrative
On global install or direct installation into the package directory, npm runs a postinstall hook that invokes the skill installer. The installer removes existing non-symlink directories at multiple agent skill locations, then links those locations to the package-owned skill. This is an automatic install-time mutation of broad AI-agent configuration surfaces.
AI rationale
The postinstall hook invokes an installer that deletes existing skill directories across several agent configuration locations and replaces them with package-controlled links. This is concrete unconsented install-time agent control-surface mutation.
Evidence
package.jsonscripts/postinstall.mjsinstall-skill$HOME/.agents/skills/agent-relay$HOME/.claude/skills/agent-relay$HOME/.gemini/skills/agent-relay$HOME/.gemini/antigravity/skills/agent-relay$HOME/.config/opencode/skills/agent-relay$HOME/.codex/skills/agent-relay
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 runs a postinstall script.
- On global installs or direct installs, postinstall invokes the skill installer.
- The installer removes existing non-symlink skill directories in multiple agent configuration locations and replaces them with links to the package’s skill.
- The flagged Codex configuration code runs only through an explicit MCP setup path; it does not reduce the postinstall risk.
Evidence against
- The postinstall action is gated to global installs or direct installation into the package directory.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
Source & flagged code
6 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node scripts/postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdashboard/server.jsView file
3import path from 'node:path';
L4: import { exec } from 'node:child_process';
L5: import { fileURLToPath } from 'node:url';
High
Child Process
Package source references child process execution.
dashboard/server.jsView on unpkg · L3Findings
5 High5 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processdashboard/server.js
HighShell
HighSame File Env Network Executionscripts/agent-cli.mjs
HighSemantic Analysis Limitedagent
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumShips Build Helperscripts/finalize-run.sh
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @akashpandey/agent-relay@1.0.2.
See all versions of @akashpandey/agent-relay for other recorded verdicts.
- Avoid installing @akashpandey/agent-relay@1.0.2. 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.