@whalent/agent@0.3.381
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is not proven malware because it has no install-time hook or verified malicious action. Deliberate full-runtime obfuscation around a process-launching remote-agent CLI leaves a material unresolved risk.
Decision evidence
public snapshot- The published CLI entrypoint is deliberately obfuscated, preventing reliable static verification of its behavior.
- The obfuscated entrypoint imports child-process support and invokes its main routine when the CLI runs.
- The package text describes a daemon that receives configurations and remote upgrade or restart commands; this remains unverified because the executable source is opaque.
- package.json has no preinstall, install, or postinstall hook; its only lifecycle hook is prepublishOnly.
- The manifest does not runtime-depend on its own package name.
- No concrete credential theft, destructive operation, or exfiltration endpoint was established from readable 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.381.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.381 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.