@whalent/agent@0.3.441
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe automatic, obfuscated global self-update behavior is a real persistence-related risk, but it is user-command triggered and lacks an install hook or evidence of credential theft or destructive activity. A warning is appropriate rather than a publication block.
Decision evidence
public snapshot- The package exposes a CLI entrypoint and has no install lifecycle hook in its metadata.
- The obfuscated CLI entrypoint invokes its wrapper update routine during normal execution.
- That entrypoint includes a routine that resolves an executable, determines a global npm prefix, and launches an installer subprocess for the wrapper.
- No preinstall, install, or postinstall hook is declared, so the observed mutation is not triggered merely by package installation.
- No concrete credential collection, unrelated network recipient, or destructive file operation was established from 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.441.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.441 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.