The credential-theft alert is not supported: the JWT is used for the Qronos flow, while the analytics pixel sends derived identifiers rather than the token itself. However, the default pixel sends a stable hostname hash and session context to a third-party tracker without clearly disclosing that collection, so this is suspicious telemetry.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Starting the CLI with a JWT whose payload has a subject; the pixel is enabled by default unless QRONOS_NO_GRAVITY_PIXEL=1.
Impact
The tracking service can link CLI sessions with a stable account-derived identifier and a stable machine-derived identifier.
Mechanism
The pixel hashes the JWT subject and hostname, then posts session data and terminal context to Gravity tracking endpoints.
Evidence
dist/main-yfs5z5ea.jsdist/index-ppxcvfgp.jsREADME.md~/.qronos/gravity/attribution.json~/.qronos/gravity/session.json
Network endpoints2
api.trygravity.ai/track/gr-events/track/gr-session