@whalent/agent@0.3.462
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe normal CLI performs opaque self-updating and global replacement without an explicit update command. Static inspection did not establish credential exfiltration, destructive activity, or an npm lifecycle attack.
Decision evidence
public snapshot- The manifest exposes dist/index.cjs as the whalent command and contains no install lifecycle hook.
- The CLI always reaches a persistence prompt and wrapper-update routine during normal execution.
- The update routine installs a selected version of its own wrapper package globally through a spawned npm command; the shipped runtime is heavily obfuscated.
- No package-install lifecycle script is declared.
- No credential collection or destination-specific exfiltration was confirmed in the inspected entrypoint.
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.462.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.462 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.