@whalent/agent@0.3.372
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThere is no install-time malicious chain or self-dependency, so blocking is not supported. However, the opaque remote-control agent runtime warrants a warning until its behavior can be independently audited.
Decision evidence
public snapshot- The published command entrypoint is deliberately obfuscated, preventing a reliable audit of its privileged runtime behavior.
- The package advertises a daemon that fetches configurations, starts workers, and accepts remote upgrade and restart commands.
- The command wrapper launches child processes and can install a separately versioned core package during runtime updates.
- package.json has no preinstall, install, or postinstall hook; prepublishOnly does not run for consumers.
- The package does not depend on its own package name.
- No concrete secret theft, destructive action, or foreign agent-control configuration write was confirmed from the inspected files.
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.372.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.372 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.