@whalent/agent@0.3.414
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is not proven malware because there is no install lifecycle trigger or confirmed exfiltration. However, automatic remote updating plus extensive obfuscation leaves a material unresolved execution risk.
Decision evidence
public snapshot- The shipped CLI and core runtime are heavily obfuscated, preventing reliable audit of their decoded behavior.
- Running the CLI automatically invokes an update routine before supervising the core runtime.
- The update routine queries npm and can install a newer wrapper release, creating an opaque remote code-update path.
- The README describes remote commands and periodic helper downloads, but the shipped implementation is not transparently reviewable.
- package.json contains only a prepublishOnly hook and no install, preinstall, or postinstall hook.
- No concrete credential-exfiltration endpoint or install-time foreign control-surface mutation 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.414.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.414 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.