@whalent/agent-core@0.3.514
Core runtime for Whalent Agent
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and inspected MCP code includes ordinary agent tool handling. Extensive obfuscation in the executable bundle leaves unresolved risk, but the inspected source does not establish a concrete attack.
Decision evidence
public snapshot- The manifest points to dist/index.cjs and declares no lifecycle hooks.
- dist/mcp.cjs uses extensive encoded identifiers and string indirection, leaving behavior difficult to verify statically.
- The MCP bundle includes configurable DNS mapping and lookup logic.
- The MCP server exposes tool calls, including profile updates, through request handlers.
- The manifest lists only a single CLI entry and ordinary runtime dependencies.
- The inspected MCP code shows agent tool operations in an explicit request handler; no concrete hidden attack was established.
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.514.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.514 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.