registry  /  thinkpool-pair  /  0.7.146

thinkpool-pair@0.7.146

Share a local coding-agent CLI (Claude Code, Codex, Gemini, Aider, …) into a ThinkPool Code room, live.

AI Security Review

scanned 7d ago · by lpm-firewall-ai

No confirmed malicious attack surface. The package is a user-invoked remote coding-agent bridge with explicit service installation and account login/provider configuration paths.

Static reason
One or more suspicious static signals were detected.
Trigger
User runs thinkpool-pair, login, provider, or install-service commands.
Impact
Room participants can drive the shared local agent/shell by design; no hidden install-time execution found.
Mechanism
Outbound realtime bridge for local coding-agent CLIs.
Rationale
Static inspection found powerful network, shell, persistence, and AI-agent control primitives, but they are disclosed, user-invoked, and central to the package's stated ThinkPool bridge functionality. No lifecycle execution, hidden payload, unrelated exfiltration, destructive persistence, or unconsented agent control-surface mutation was identified.
Evidence
package.jsonREADME.mdbridge.mjsservice.mjsaccount.mjsauth-store.mjsprovider.mjsclaude-session.mjs~/.thinkpool-pair/auth.json~/.thinkpool-pair/provider.json~/.thinkpool-pair/<ROOM>/~/Library/LaunchAgents/io.thinkpool.pair.*.plist~/.config/systemd/user/io.thinkpool.pair.*.service%APPDATA%/Microsoft/Windows/Start Menu/Programs/Startup/thinkpool-pair-*.cmd/tmp/thinkpool-pair/<ROOM>/tmp/thinkpool-mockups/<ROOM>
Network endpoints6
daytvtakmlixpfbbqzjd.supabase.cothinkpool.ioregistry.npmjs.org/thinkpool-pair/latestapi.anthropic.comopenrouter.ai/apiapi.z.ai/api/anthropic

Decision evidence

public snapshot
AI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for block
  • bridge.mjs embeds Supabase anon JWT and uses network APIs to ThinkPool/Supabase.
  • service.mjs can install launchd/systemd/Startup persistence, but only via install-service subcommand.
  • bridge.mjs spawns local agent CLIs/PTYs and accepts room-originated terminal actions by design.
Evidence against
  • package.json has no install/preinstall/postinstall lifecycle hooks; only bin is bridge.mjs.
  • README.md describes a local coding-agent bridge matching bridge.mjs behavior.
  • service.mjs validates room labels with /^[A-Za-z0-9]{2,16}$/ before shell/service interpolation.
  • auth-store.mjs/provider.mjs store user-selected credentials locally under ~/.thinkpool-pair with 0600 for secrets.
  • Network endpoints are package-aligned: thinkpool.io, Supabase project, npm registry, optional user-configured providers.
  • No credential harvesting or exfiltration outside the declared bridge/login/provider flows found.
Behavioral surface
Source
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
Supply chain
HighEntropyStringsUrlStrings
Manifest
NoLicense
scanned 27 file(s), 559 KB of source, external domains: api.anthropic.com, api.z.ai, daytvtakmlixpfbbqzjd.supabase.co, openrouter.ai, registry.npmjs.org, thinkpool.io, www.apple.com

Source & flagged code

3 flagged · loading source
bridge.mjsView file
94patternName = supabase_service_key severity = critical line = 94 matchedText = const SU...tqo'
Critical
Critical Secret

Package contains a critical-looking secret pattern.

bridge.mjsView on unpkg · L94
94patternName = supabase_service_key severity = critical line = 94 matchedText = const SU...tqo'
Critical
Secret Pattern

Supabase service role key (JWT) in bridge.mjs

bridge.mjsView on unpkg · L94
service.mjsView file
22import path from 'node:path' L23: import { execSync } from 'node:child_process' L24: ... L26: // exactly one account service per machine (a second install replaces it). L27: // Room codes flow UNESCAPED into launchctl/systemd shell strings + plist paths, so L28: // this is the security chokepoint: reject anything that isn't a plain alnum code ... L44: // `home` is the platform-correct, runtime-expanded home token ("$HOME" on darwin under L45: // /bin/bash; "$$HOME" inside a systemd unit so systemd emits a literal $HOME to bash). L46: const cacheWipe = (home) => `rm -rf ${home}/.npm/_npx/*/node_modules/thinkpool-pair 2>/dev/null` ... L48: // The version installing the service. By DEFAULT the service is pinned to this exact L49: // version (not @latest) so a future bad npm publish can't auto-roll to every machine's L50: // always-on bridge — that's what spread the broken 0.7.49 on 2026-06-22. Updates become
Medium
Install Persistence

Source writes installer persistence such as shell profile or service configuration.

service.mjsView on unpkg · L22

Findings

2 Critical3 Medium5 Low
CriticalCritical Secretbridge.mjs
CriticalSecret Patternbridge.mjs
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistenceservice.mjs
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License