@whalent/agent@0.3.428
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiNo install-hook abuse or concrete malicious payload was established, but the opaque runtime combines persistence, self-update, process control, and diagnostic upload. This is an unresolved dangerous capability rather than a clean, auditable CLI.
Decision evidence
public snapshot- The published CLI and its 16 MB core bundle are deliberately obfuscated, preventing meaningful verification of their runtime behavior.
- Launching the CLI invokes persistence prompting, wrapper updates, and core-process supervision.
- The core contains a debug-log archive upload routine, including calls that pass platform and authentication-related runtime values.
- The executable is a user-invoked CLI rather than an npm install hook.
- package.json has no preinstall, install, or postinstall script; its only lifecycle script is prepublishOnly.
- No concrete secret-stealing payload, destructive action, or foreign AI-agent configuration write was established from the inspected source.
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.428.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.428 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.