@whalent/agent@0.3.503
⚠ Under reviewStable wrapper for Whalent Agent core runtime
AI Security Review
scanned 10d ago · by lpm-firewall-aiThe manifest does not show an npm install hook, but the shipped runtime is heavily obfuscated and includes an agent skill installation path whose activation and safeguards could not be resolved. The evidence is insufficient to classify the package as clean or malicious.
Decision evidence
public snapshot- The flagged location in dist/mcp.cjs selects platform skill directories, including paths under the user home or an agent-managed location, but its obfuscated context does not reveal activation or consent.
- The bundle has a skill installer that writes supplied file maps and a downloader that sends a bearer token to a URL built from a runtime-provided base; the caller chain and effective destination remain unclear.
- The main entrypoint is heavily obfuscated, and the package manifest lists only bundled distribution files, limiting reliable tracing of runtime behavior.
- The inspected manifest shows a prepublishOnly build command; no preinstall, install, or postinstall hook appears in its script list.
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.503.
See all versions of @whalent/agent for other recorded verdicts.
- Review the evidence and your use of @whalent/agent@0.3.503 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.