@funny-booth/agent-core@0.1.29
AIエージェント起動CLI(共有ランチャー + MCPサーバー)
AI Security Review
scanned 7d ago · by lpm-firewall-aiThe shipped runtime is deliberately obfuscated, leaving the feedback destination and some behavior difficult to verify. Inspected source does not establish a concrete attack, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The publish script explicitly runs an obfuscation step, and the shipped launcher and feedback modules use encoded strings and indirect property lookups, which limits static verification of their behavior.
- The launcher checks the npm registry for a newer package version and the feedback module sends a report when selected failures occur; the report recipient is obscured in the inspected code.
- The MCP entrypoint requires portal credentials from its environment and uses the local vault for token reads and saves.
- The manifest has no preinstall, install, or postinstall hook; its only publish hook builds the package.
- The inspected launcher update check targets registry.npmjs.org, and the MCP entrypoint requires explicit portal credentials to start. No concrete credential theft, destructive action, or remote code execution was established.
Source & flagged code
3 flagged · loading sourceSource contains an obfuscated payload loader that reconstructs and executes hidden code.
dist/feedback.jsView on unpkg · L1Package source references dynamic require/import behavior.
dist/feedback.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @funny-booth/agent-core@0.1.29.
See all versions of @funny-booth/agent-core for other recorded verdicts.
- Review the evidence and your use of @funny-booth/agent-core@0.1.29 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.