@whalent/agent-core@0.3.524
Core runtime for Whalent Agent
AI Security Review
scanned 4d ago · by lpm-firewall-aiThe manifest declares no install hook, and inspected excerpts do not establish concrete malicious behavior. The substantial obfuscation in an executable bundle leaves a real unresolved risk, so this warrants a warning rather than a clean verdict or block.
Decision evidence
public snapshot- The manifest points the package entrypoint and executable command at dist/index.cjs and declares no lifecycle scripts.
- The dist/mcp.cjs executable begins with heavily obfuscated code, leaving its behavior difficult to verify from static inspection.
- The MCP bundle includes an interface for handling tool requests, consistent with runtime functionality, but the inspected excerpts do not establish an attack.
- No install lifecycle hook is declared in package.json.
- The inspected source did not establish credential theft, unauthorized account actions, or another concrete 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.524.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.524 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.