@whalent/agent@0.3.378
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package is not malicious under the install-hook policy because it has no registry install lifecycle hook. Its obfuscated self-updating agent wrapper is nevertheless an unresolved dangerous capability and should be warned on.
Decision evidence
public snapshot- The published CLI entrypoint is deliberately obfuscated, preventing normal source audit.
- When the CLI runs, the wrapper includes automatic update logic.
- The wrapper can install a core package globally through npm at runtime.
- The manifest has no preinstall, install, or postinstall hook.
- The executable behavior is triggered by invoking the whalent command, not by package installation.
- No hard-coded network endpoint or direct credential-exfiltration path was confirmed 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.378.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.378 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.