@whalent/agent@0.3.457
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package is an obfuscated Whalent CLI with no install hook and no self-install chain, but its shipped bundle still selects agent config directories and calls the vendor host. That dual-use runtime is user-invoked and not a proven covert attack, so it warrants a warning rather than a block.
Decision evidence
public snapshot- package.json exposes only the user-run whalent bin at dist/index.cjs and has no preinstall, install, or postinstall hook.
- dist/mcp.cjs is an obfuscated runtime bundle that fetches a host checked against memory.whalent.com and maps platforms to .claude or .agents from the user home.
- The same-version optional dependency is the sibling package @whalent/agent-core, not a nested install of @whalent/agent.
- No automatic npm lifecycle hook mutates agent config or runs on install.
- The visible fetch host matches the Whalent Memory product named in the package.
- No hidden recipient, credential copy, or self-install chain was readable in the inspected source.
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.457.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.457 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.