@whalent/agent@0.3.418
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package is too deliberately obfuscated to establish a clean verdict, and its runtime update and remote-command features create real risk. It does not meet the policy threshold for malicious install-hook abuse because installation has no automatic lifecycle trigger.
Decision evidence
public snapshot- The executable bundles are deliberately obfuscated, preventing meaningful audit of their runtime network, file, and command behavior.
- The CLI contains code for spawning processes and automatically installing or updating its runtime when the user runs it.
- The README describes a daemon that accepts remote upgrade and restart commands, creating a remotely directed capability.
- The manifest has no npm preinstall, install, or postinstall hook.
- There is no runtime dependency on the package's own name; the optional core package has a different name.
- The Python sidecar is a local Jupyter-kernel NDJSON bridge and does not itself make network requests.
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.418.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.418 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.