@whalent/agent@0.3.486
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 21d ago · by lpm-firewall-aiThe active, heavily obfuscated runtime leaves a real unresolved execution risk, supporting a warning rather than a clean verdict. No concrete malicious chain was established, and the inspected MCP compilation does not substantiate the scanner's payload-loader claim.
Decision evidence
public snapshot- The active wrapper launches a selected core script through child_process and forwards the process environment; extensive string obfuscation obscures this execution path.
- dist/core.cjs contains extensive obfuscation and exceeds the inspection tool's source limit, leaving the launched runtime's behavior unresolved.
- package.json has no registry-install lifecycle hooks or runtime self-dependency.
- The inspected dynamic compilation in dist/mcp.cjs builds schema validation code, which does not establish a hidden payload loader.
- No concrete exfiltration, destructive action, or unconsented agent configuration mutation was established.
- Child processes and authenticated platform requests are consistent with an agent CLI.
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.486.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.486 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.