@whalent/agent-core@0.3.456
Core runtime for Whalent Agent
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package does not show a concrete malicious lifecycle chain or confirmed exfiltration. Its opaque executable code combined with remotely supplied MCP capabilities leaves a material unresolved agent-control risk.
Decision evidence
public snapshot- The manifest exposes a CLI entrypoint and has no npm lifecycle scripts.
- Both executable bundles are deliberately obfuscated, preventing reliable static verification of their full behavior.
- The MCP executable fetches a remote tool manifest using a bearer token and invokes remote tools through the configured platform URL.
- No preinstall, install, or postinstall hook is declared.
- No concrete secret-harvesting, destructive action, or unsolicited network destination was established from the inspected paths.
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.456.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.456 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.