@whalent/agent@0.3.421
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is not proven malware, but the obfuscated executable runtime and code-execution capability leave a material unresolved risk. The absence of install hooks and a concrete attack chain supports warning rather than blocking publication.
Decision evidence
public snapshot- The published CLI is deliberately obfuscated; its build configuration includes an unobfuscated fast mode and a JavaScript obfuscator.
- The package exposes an executable entry point whose opaque bundled runtime cannot be meaningfully audited.
- Its Jupyter sidecar accepts supplied code and forwards it to a kernel for execution.
- The manifest has no preinstall, install, or postinstall lifecycle hook; prepublishOnly is not run when consumers install the package.
- It does not declare a runtime dependency on its own package name.
- No concrete credential theft, destructive action, or hard-coded network endpoint was established from the inspected files.
Source & flagged code
6 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.421.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.421 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.