@whalent/agent@0.3.363
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has no registry install lifecycle hook, but opaque runtime update and manifest-resolution code prevents a clean determination. The evidence supports a non-blocking warning for a possible staged payload path, not proof of malware.
Decision evidence
public snapshot- The executable entrypoint is an intentionally obfuscated wrapper that contains an automatic wrapper-update check.
- The 15 MB obfuscated core accepts a helper manifest URL from an environment variable, leaving remotely supplied helper resolution opaque to static review.
- The package is a CLI wrapper, so these behaviours activate when its command is run.
- package.json has no preinstall, install, or postinstall lifecycle hook.
- The inspected manifest does not runtime-depend on its own package name.
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.363.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.363 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.