@whalent/agent-core@0.3.507
Core runtime for Whalent Agent
AI Security Review
scanned 8d ago · by lpm-firewall-aiStatic inspection found no confirmed malicious behavior or install hook. The obfuscated executable entrypoint leaves material runtime behavior unresolved, so the package should be warned rather than marked clean or blocked.
Decision evidence
public snapshot- The package manifest routes its main entrypoint and CLI to dist/index.cjs, whose full runtime behavior remains unresolved after bounded inspection.
- The included MCP bundle uses heavily encoded identifiers and a decoder wrapper.
- The manifest declares no lifecycle scripts, and the observed dynamic function construction in the MCP bundle is part of local code generation rather than evidence of a remote payload loader.
- The package describes itself as the Whalent Agent runtime and depends on SSH and pseudo-terminal libraries, consistent with that stated role.
- No concrete credential theft, destructive behavior, or payload execution was confirmed in the inspected excerpts.
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.507.
See all versions of @whalent/agent-core for other recorded verdicts.
- Review the evidence and your use of @whalent/agent-core@0.3.507 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.