@whalent/agent@0.3.370
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe active, obfuscated CLI includes automatic self-update behavior and a persistence-related prompt, which leaves a meaningful agent-runtime lifecycle risk. Static inspection did not establish a concrete malicious payload or data theft.
Decision evidence
public snapshot- package.json exposes dist/index.cjs as both the main module and the whalent CLI.
- The active CLI entrypoint invokes its persistence check and wrapper-update routine.
- The update routine resolves a newer package version and passes it to installWrapperVersion before respawning.
- package.json contains no npm preinstall, install, or postinstall lifecycle hook.
- No credential collection, endpoint, or exfiltration send sink was confirmed in the inspected entrypoint.
Source & flagged code
5 flagged · loading sourceSource contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/index.cjsView on unpkg · L1Package source references dynamic require/import behavior.
dist/index.cjsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @whalent/agent@0.3.370.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.370 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.