@whalent/agent@0.3.420
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is not a confirmed malicious install hook, but opaque automatic replacement of the running package is a real unresolved supply-chain risk. Warn rather than block because activation requires an explicit CLI invocation and no concrete harmful payload was established.
Decision evidence
public snapshot- The manifest exposes dist/index.cjs as the executable CLI entry point.
- The CLI entry point is deliberately obfuscated and automatically checks for and installs a newer release with npm when the user runs the command.
- The wrapper can respawn itself after updating, creating a runtime-delivered code path that cannot be meaningfully audited from this release.
- package.json has no preinstall, install, or postinstall hook.
- The package does not declare itself as a runtime dependency.
- No concrete secret theft, destructive action, or foreign AI-agent configuration write was confirmed.
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.420.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.420 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.