@whalent/agent-core@0.3.509
⚠ Under reviewCore runtime for Whalent Agent
AI Security Review
scanned 9d ago · by lpm-firewall-aiStatic inspection found agent skill installation and download helpers in an obfuscated bundle, but did not establish their callers or consent boundary. Manual review is appropriate because no concrete attack or benign activation path was confirmed.
Decision evidence
public snapshot- The manifest points its CLI entrypoint to bundled code and declares no lifecycle hook.
- The bundle maps skills to user, workspace, or managed agent directories and contains a helper that writes skill files there; its caller and activation were not resolved.
- A bundle helper downloads skill files from a configured base URL using an authorization header; its caller and destination configuration were not resolved.
- The manifest lists only ssh2 and node-pty as dependencies and contains no install lifecycle script.
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-core@0.3.509.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@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.