@whalent/agent@0.3.448
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe automatic global self-update and opaque implementation create a meaningful dangerous capability, but static evidence does not prove an active malicious attack. The package has no install lifecycle hook.
Decision evidence
public snapshot- The package exposes dist/index.cjs as its executable and has no npm install lifecycle hook.
- The executable runs a synchronous npm global install for WRAPPER_PKG_NAME at a selected version.
- On normal executable startup it invokes the update routine before supervising the core process.
- No install, preinstall, or postinstall script is declared.
- The observed install targets the package's own wrapper name, not a foreign agent configuration surface.
- No credential collection or network exfiltration sink was established in the inspected entrypoint excerpts.
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.448.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.448 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.