thalamus@1.5.92
⚠ Under reviewMobile and Web client for Claude Code
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe manifest and installer show that package installation extracts an executable archive. Its expanded contents exceeded the available inspection limit, so I cannot determine whether this package is malicious.
Static reason
High-risk behavior combination matched malicious policy.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
Installing the package runs its postinstall hook.
Impact
The extracted binary’s behavior remains unresolved, so package safety cannot be determined from this inspection.
Mechanism
The hook extracts the platform-specific difftastic archive and preserves executable permissions; the archive analysis could not assess the expanded binary’s behavior.
AI rationale
The manifest and installer show that package installation extracts an executable archive. Its expanded contents exceeded the available inspection limit, so I cannot determine whether this package is malicious.
Evidence
tools/archives/difftastic-arm64-linux.tar.gz.lpm-inspection-LQDxBx/0-eb2deb082b1c.txtpackage.jsonscripts/unpack-tools.cjsdist/api-D0kNPgpd.cjs
Decision evidence
public snapshotAI called this Manual Review at 91.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The package postinstall hook runs scripts/unpack-tools.cjs.
- The installer selects a platform-specific difftastic archive, extracts it, and preserves executable permissions.
- The archive analysis reports that expanded content exceeded its inspection limit, leaving the binary’s behavior unresolved.
Evidence against
- The inspected source associates the archive with difftastic and ripgrep tooling; it does not establish malicious behavior.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
Source & flagged code
20 flaggedpackage.jsonView file
•scripts.postinstall = node scripts/unpack-tools.cjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkgbin/thalamus-mcp.mjsView file
2L3: import { spawn } from 'child_process';
L4: import { fileURLToPath } from 'url';
High
Child Process
Package source references child process execution.
bin/thalamus-mcp.mjsView on unpkg · L2dist/index-CWZbHZDs.cjsView file
9var persistence = require('./persistence-CYBxCuOZ.cjs');
L10: var child_process = require('child_process');
L11: var psList = require('ps-list');
...
L14: var path = require('node:path');
L15: var axios = require('axios');
L16: var fs$1 = require('fs/promises');
...
L103: }
L104: const body = await res.json().catch(() => null);
L105: if (res.status === 404) return body?.error === "Not found" ? { kind: "not-found" } : { kind: "retry" };
...
L555: }
L556: if (process.platform !== "darwin") {
L557: logger.logger.debug("[caffeinate] Not on macOS, skipping caffeinate");
Findings
4 Critical13 High6 Medium5 Low
CriticalHardcoded Runtime Data Exfiltrationdist/index-CWZbHZDs.cjs
CriticalEncrypted Payload Temp Executiondist/index-CWZbHZDs.cjs
CriticalTrigger Reachable Dangerous Capabilitydist/api-D0kNPgpd.cjs
CriticalPrevious Version Dangerous Deltadist/index-CWZbHZDs.cjs
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processbin/thalamus-mcp.mjs
HighShelldist/index-CWZbHZDs.cjs
HighSame File Env Network Executiondist/api-D0kNPgpd.cjs
HighCredential Redirect Persistencedist/api-D0kNPgpd.cjs
HighCommand Output Exfiltrationdist/api-D0kNPgpd.cjs
HighSandbox Evasion Gated Capabilitydist/index-CWZbHZDs.cjs
Affected versions and remediation
This report applies to thalamus@1.5.92.
See all versions of thalamus for other recorded verdicts.
- Review the evidence and your use of thalamus@1.5.92 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.