@adithyasak/t3@0.1.4-adi.1
Node.js WebSocket server for the T3 Code app.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe flagged worker is part of a user-invoked CLI and handles explicit Claude session-history operations. The reported dynamic execution and external request resolve to an empty-function runtime check and a bounded connectivity probe; no malicious attack chain was found.
Decision evidence
public snapshot- The package exposes a `t3` command, whose entry point dispatches explicit CLI commands.
- The history worker requires a session ID and handles only session message retrieval or session forking; unknown operations throw an error.
- The flagged `new Function` call creates an empty function inside a runtime support check; it does not execute remotely supplied code.
- The request to 1.1.1.1 is an HTTP HEAD connectivity probe with a one-second timeout and returns only a success boolean.
- The CLI and its Claude agent SDK use child processes, credentials, network access, and local session data as part of coding-agent and session-history functions.
- The explicit connectivity probe contacts 1.1.1.1 when its internet-access check runs.
Source & flagged code
15 flaggedSource appears to send environment or credential material to an external endpoint.
dist/claudeHistoryWorker-D95roNnb.mjsView on unpkg · L10Source matches reverse-shell style process and socket wiring.
dist/claudeHistoryWorker-D95roNnb.mjsView on unpkg · L10Findings
Affected versions and remediation
This report applies to @adithyasak/t3@0.1.4-adi.1.
See all versions of @adithyasak/t3 for other recorded verdicts.
- Review the evidence and your use of @adithyasak/t3@0.1.4-adi.1 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.