@whalent/agent@0.3.427
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiNo registry-install lifecycle hook or concrete malicious payload was found, so blocking is not supported. The opaque executable and agent-control capabilities leave a material unresolved runtime risk.
Decision evidence
public snapshot- The published CLI entrypoint is deliberately obfuscated, preventing meaningful verification of its filesystem, process, and network behavior.
- When run, the wrapper invokes persistence prompting, update, and supervision routines.
- The runtime is an agent/daemon that launches a Jupyter kernel sidecar capable of executing supplied notebook code.
- package.json has no preinstall, install, or postinstall hook; its only lifecycle hook is prepublishOnly.
- No concrete credential exfiltration, destructive action, or install-time mutation 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.427.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.427 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.