On connection, the executor sends all process environment variables to the configured Iridium endpoint, which can expose credentials for unrelated services. The configured endpoint and pairing approval limit when this happens, but the source does not disclose the environment transfer as part of that approval.
Static reason
No blocking static signals were detected.
Trigger
After an Iridium URL is configured and pairing succeeds, the executor connects and sends its hello payload; it also reconnects automatically.
Mechanism
The hello payload defaults to all process.env entries and is sent over an authenticated WebSocket to the configured endpoint.
Attack narrative
After the user configures an Iridium endpoint and approves pairing, the executor sends a hello payload containing every environment variable from the dsh process over an authenticated WebSocket. That can disclose credentials for unrelated services to the configured endpoint; the pairing information described by the package does not disclose this environment transfer.
Evidence
executor.jsindex.js$DSH_HOME/remote-iridium/token/<host>
Network endpoints1
User-configured http(s) Iridium endpoint; WebSocket path /api/exec