@whalent/agent@0.3.507
⚠ Under reviewStable wrapper for Whalent Agent core runtime
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe manifest has no automatic install hook, and the inspected source does not establish a concrete attack. Obfuscated runtime code and a very large core bundle leave material behavior unresolved, so manual review is appropriate.
Decision evidence
public snapshot- The CLI entrypoint uses a rotated string table and heavily obfuscated identifiers.
- The wrapper checks for a newer package version during runtime, but the obfuscated implementation leaves the update effects unresolved.
- The CLI launches a separate core script, whose behavior could not be fully resolved from the available source excerpts.
- The MCP bundle also contains obfuscated dynamic function generation; its full behavior remains unresolved.
- The manifest declares only a prepublishOnly build script, with no preinstall, install, or postinstall hook.
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@0.3.507.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@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.