@whalent/agent@0.3.509
⚠ Under reviewStable wrapper for Whalent Agent core runtime
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe manifest shows no install-time execution hook, but obfuscated runtime and agent-integration paths prevent resolving behavior and consent. Manual review is warranted without a confirmed attack.
Decision evidence
public snapshot- package.json exposes a CLI and lists `prepublishOnly` as a build command, with no npm install lifecycle hook.
- dist/index.cjs parses command-line arguments, but its obfuscated dispatch does not make the runtime behavior clear.
- dist/mcp.cjs selects agent directories and contains a skill-file writer helper; its caller and consent path remain unresolved.
- The manifest shows no `preinstall`, `install`, or `postinstall` hook.
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.509.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.509 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.