@whalent/agent@0.3.429
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has unresolved risk because its main executable is deliberately obfuscated while controlling updates and agent workers. Static inspection found no completed malicious install chain or concrete exfiltration behavior.
Decision evidence
public snapshot- The executable entry point is deliberately obfuscated, preventing meaningful transparent auditing of its privileged CLI behavior.
- The wrapper contains an automatic update path and invokes npm-related runtime installation logic.
- The package describes a daemon that downloads helper releases, starts configured workers, and accepts gateway commands.
- The manifest has only a prepublishOnly hook, not an install-time lifecycle hook.
- No plaintext hard-coded network endpoint, credential exfiltration path, or destructive action was confirmed by static inspection.
- The bundled Python sidecar is a local Jupyter-kernel protocol bridge.
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.429.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.429 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.