@whalent/agent@0.3.413
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package is unusually opaque and has powerful runtime behavior, but source inspection found no automatic registry-install execution or concrete malicious action. The observed behavior is tied to its declared CLI entry point.
Decision evidence
public snapshot- The CLI entry point is heavily obfuscated and invokes persistence, self-update, and supervision logic when the user runs it.
- The package can launch its bundled core as a child process.
- The manifest has no preinstall, install, or postinstall hook; its only lifecycle hook is prepublishOnly.
- The entry point is a declared user-invoked bin command, not an import-time installer.
- No self-dependency on @whalent/agent, credential harvesting, or concrete secret-exfiltration path 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.413.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.413 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.