@whalent/agent@0.3.470
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 25d ago · by lpm-firewall-aiThe package exposes a guarded capability to alter AI-agent MCP configuration with caller-supplied launch details. This warrants a warning for agent-extension lifecycle risk, not a block, because no automatic or covert activation was found.
Decision evidence
public snapshot- The MCP handler registers caller-provided command, arguments, and environment values through an MCP configuration injection function.
- The Codex configuration helper creates or rewrites config.toml MCP-server entries.
- Package metadata has build and start scripts but no npm install lifecycle hook.
- No automatic install-time execution was found in package metadata.
- The configuration write requires a request to the running MCP service; no covert default registration was identified.
Source & flagged code
8 flagged · loading sourceA single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/mcp.cjsView on unpkg · L4Source contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/mcp.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @whalent/agent@0.3.470.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.470 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.