@whalent/agent@0.3.375
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is suspicious because high-impact remote-management behavior is hidden behind obfuscation, so its safety cannot be verified from the published source. It is not malicious under the install-hook policy because no automatic registry-install trigger or concrete attack behavior was found.
Decision evidence
public snapshot- The executable entrypoint is heavily obfuscated, preventing normal audit of its runtime behavior.
- The entrypoint loads child-process support and launches processes with inherited environment variables.
- Package text describes a daemon that receives remote commands and downloads and activates helper manifests.
- The package is a CLI agent that can start managed AI workers after an explicit command.
- package.json has no preinstall, install, or postinstall hook.
- The only lifecycle script is prepublishOnly, which is not run for registry consumers.
- No concrete credential theft, destructive action, or unconsented install-time mutation 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.375.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.375 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.