@whalent/agent@0.3.440
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiAutomatic global self-updating from an obfuscated CLI is a concrete persistence risk. The absence of a registry install hook prevents classifying the observed behavior as malicious install-hook abuse.
Decision evidence
public snapshot- The package exposes the obfuscated wrapper as both its main module and CLI.
- The CLI automatically checks for a newer wrapper release when it runs.
- The updater invokes npm globally to install the selected wrapper version.
- No npm preinstall, install, or postinstall hook is declared.
- The inspected metadata has no automatic registry-install lifecycle hook.
- The inspected updater uses a named package version rather than an arbitrary shell command.
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.440.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.440 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.