@whalent/agent@0.3.513
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe executable entrypoint and bundled module are substantially obfuscated, and the entrypoint references child_process through a dynamically assembled import. The inspected excerpts do not establish an attack chain, so this remains an unresolved risk rather than a confirmed malicious behavior.
Decision evidence
public snapshot- The manifest exposes dist/index.cjs as the package entrypoint and three executable commands.
- The entrypoint uses heavily obfuscated identifiers and dynamically constructs a child_process module name.
- The bundled dist/mcp.cjs also begins with an obfuscated wrapper; its large size and obfuscation prevent resolving the flagged loader behavior from bounded excerpts.
- The visible new Function call in dist/mcp.cjs is in bundled schema-validation code, but that does not resolve the separate obfuscated behavior.
- The only manifest lifecycle script is prepublishOnly, which runs a build; no install hook is declared.
- The visible dynamic code generation excerpt is consistent with bundled schema validation and does not itself establish an attack.
Source & flagged code
7 flagged · loading sourceSource contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/mcp.cjsView on unpkg · L1A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/mcp.cjsView on unpkgFindings
Affected versions and remediation
This report applies to @whalent/agent@0.3.513.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.513 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.