@whalent/agent-core@0.3.513
Core runtime for Whalent Agent
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe package has no install hook, and inspected command execution is consistent with its stated agent-runtime purpose. Extensive obfuscation across its runtime bundles prevents a clean assessment, but the inspected source does not establish a concrete attack, so warn rather than block.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and contains no install lifecycle scripts.
- The MCP executable uses a string-table rotation pattern that obscures its behavior; the bundled source is difficult to assess statically.
- The main CLI bundle is also heavily obfuscated and includes command execution, leaving its full behavior unresolved.
- The package describes itself as an agent runtime and declares SSH and terminal dependencies consistent with command-capable agent functionality.
- The inspected dynamic function construction in the MCP bundle occurs in bundled schema compilation code; it does not establish a payload attack.
Source & flagged code
7 flagged · loading sourceSource contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/mcp.cjsView on unpkg · L1A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/mcp.cjsView on unpkgFindings
Affected versions and remediation
This report applies to @whalent/agent-core@0.3.513.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.513 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.