@whalent/agent@0.3.407
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis package does not contain an npm install hook or a self-dependency, but its obfuscated runtime global updater with lifecycle-script allowance is a concrete unresolved execution risk. Static inspection cannot establish malicious intent or a confirmed payload.
Decision evidence
public snapshot- The published CLI entry point and its 16 MB core bundle are deliberately string and control-flow obfuscated, which prevents meaningful static verification of their behavior.
- When the CLI runs, the wrapper invokes npm with a global install argument for a wrapper package and enables selected lifecycle scripts.
- The executable can run child processes and carries an opaque remote-update mechanism, leaving a supply-chain execution surface that cannot be safely resolved from the shipped source.
- package.json has no preinstall, install, or postinstall hook; its only lifecycle-like hook is prepublishOnly.
- The manifest has no dependency on its own package name.
- No concrete credential theft, destructive command, or exfiltration endpoint was recoverable 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.407.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.407 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.