@whalent/agent@0.3.376
Stable wrapper for Whalent Agent core runtime
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThis is a real but user-invoked remote-agent capability hidden behind extensive obfuscation. It warrants a warning, not a publish block, because no automatic lifecycle abuse or concrete malicious action was confirmed.
Decision evidence
public snapshot- Both executable JavaScript artifacts are deliberately obfuscated, preventing transparent verification of their behavior.
- The user-invoked CLI prompts for persistence, updates its wrapper, and supervises a core process.
- The core creates a daemon using a token and gateway configuration, creating a remote-control capability.
- The manifest has no preinstall, install, or postinstall hook; its only lifecycle hook is prepublishOnly.
- The package does not runtime-depend on its own package name; its optional core dependency has a different name.
- No concrete credential theft, destructive action, or automatic install-time mutation was established from source inspection.
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.376.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.376 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.