@whalent/agent@0.3.417
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a high-risk, opaque remote agent and self-updating CLI, but it lacks an automatic registry-install trigger or a confirmed malicious payload. It warrants a warning rather than a publication block.
Decision evidence
public snapshot- The command-line wrapper is deliberately obfuscated; the manifest includes an obfuscator as a development dependency.
- At runtime, the wrapper checks for a newer release and invokes npm to globally install its own package name and version.
- The package describes a daemon that fetches agent configuration, starts workers, and accepts remote upgrade and restart commands.
- The manifest has no preinstall, install, or postinstall hook; its only lifecycle entry is prepublishOnly.
- The risky behavior is activated by running the whalent command, not by package installation.
- No concrete credential theft, destructive command, or undisclosed external endpoint 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.417.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.417 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.