@whalent/agent@0.3.366
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has no install-time lifecycle hook, but its normal CLI entrypoint performs an opaque self-update through npm and permits scripts. This is a dangerous active capability rather than confirmed malware.
Decision evidence
public snapshot- The manifest exposes dist/index.cjs as the executable entrypoint and contains no install lifecycle hook.
- The executable entrypoint automatically calls its wrapper update routine when the CLI runs.
- The update routine invokes a global npm install for the wrapper package and supplies an argument enabling selected package scripts.
- The executable is deliberately obfuscated, preventing transparent inspection of its update and persistence paths.
- No preinstall, install, or postinstall hook is declared in the manifest.
- No concrete credential collection or exfiltration endpoint was established from the inspected entrypoint.
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.366.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.366 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.