@whalent/agent@0.3.377
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete malicious install or exfiltration behavior was established, but extensive deliberate obfuscation combined with remote command and runtime update capability leaves a real unresolved risk. Warn rather than block because activation requires explicit CLI use and there is no self-dependency lifecycle chain.
Decision evidence
public snapshot- The published CLI entrypoint is fully obfuscated, and the manifest includes an obfuscator dependency.
- The daemon is designed to periodically obtain, download, and activate helper releases at runtime.
- The daemon accepts gateway commands and manages agent workers, creating a remote-control capability when explicitly run.
- The manifest has only a prepublish hook; it has no install, postinstall, or preinstall hook.
- No runtime dependency repeats this package name.
- No hardcoded network endpoint or direct credential-exfiltration path was identified.
- The observed update and worker behavior is aligned with the package's stated agent-daemon function.
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.377.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.377 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.