thalamus@1.5.50
⚠ Under reviewMobile and Web client for Claude Code
AI Security Review
scanned 28d ago · by lpm-firewall-aiInspected source does not substantiate the scanner’s alleged encrypted payload execution or a concrete attack. The clean disposition is blocked by the required nine-path citation coverage exceeding the eight-citation limit, so this remains manual review rather than a malicious finding.
Decision evidence
public snapshot- The postinstall hook invokes an unpacker that extracts platform-specific bundled utilities into the package tools directory.
- The flagged settings code derives ordinary Claude configuration and project paths; the inspected excerpts show path selection and transcript-related helpers, not installation-time configuration mutation.
- The CLI MCP wrapper imports its package-owned bridge when launched, and the OAuth endpoints shown are Claude and Anthropic endpoints.
- Static hints allege encrypted payload execution, but inspection found no corresponding decrypt-and-execute path in the main bundle; observed subprocesses are associated with CLI, git, platform, or daemon operations.
- The archive unpacker selects named platform archives and extracts them to tools/unpacked; no remote payload fetch or foreign agent configuration write was established.
Source & flagged code
16 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references child process execution.
bin/thalamus-mcp.mjsView on unpkg · L2Findings
Affected versions and remediation
This report applies to thalamus@1.5.50.
See all versions of thalamus for other recorded verdicts.
- Review the evidence and your use of thalamus@1.5.50 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.