独家：SpaceXAI 的 Grok Bot 在浏览器请求中嵌入了一个源自账户的 ID
该16字符值源自经过身份验证的 Cursor 帐户，并通过 Chrome 的 User-Agent 请求头发送到外部网站。
By RuntimeWire Staff · Published
RUNTIMEWIRE INVESTIGATION — Exclusive
Original reporting by RuntimeWire, based on reverse engineering, data analysis, testing.
为何重要
Grok Bot 通过常规的 HTTP 元数据为网站提供一个持久的识别密钥，网站可以通过该密钥在服务器和分析日志中留下记录，而不受类 cookie 的控制。
Reporting record
Finding
Grok Bot’s cloud Chrome browser sent an unrelated website a 16-character pseudonymous identifier that the shipped client deterministically derives from the authenticated Cursor account’s JWT subject and appends to the User-Agent header.
How we verified
Methods: reverse engineering, data analysis, testing.
Inspection of Grok Bot for Windows 0.16.0 showed that the client hashes the authenticated Cursor account’s JWT sub claim with SHA-256, retains the first 16 hexadecimal characters and writes the result to /tmp/sand-ua-user. Shipped browser configuration describes the resulting suffix as GrokAgent/1.0 (u:<owner>) and applies it to Chrome launches and new tabs. A signed-in live test using Grok Bot’s graphical browser returned the same format from https://httpbingo.org/user-agent. A ChatGPT for Windows control returned a standard Chrome user agent without a product or account suffix. The full Grok Bot identifier has been redacted.
RuntimeWire verified the Windows package metadata, extracted app.asar and inspected the shipped source maps. We traced the browser identifier from the authenticated JWT subject through its SHA-256 derivation, 16-character truncation, local stamp file and Chrome user-agent configuration. We then instructed a signed-in Grok Bot to open Httpbingo’s user-agent endpoint through graphical Chrome, explicitly prohibiting terminal commands and other HTTP clients. The external server returned GrokAgent/1.0 and a 16-character u: value matching the implementation. RuntimeWire repeated the endpoint test through ChatGPT for Windows as a control and compared the returned headers. Only one Grok Bot account was tested.
Tested versions:
- Grok Bot for Windows 0.16.0
- managed Chrome 151.0.0.0
- ChatGPT for Windows control — app version not recorded
Reproduction
RuntimeWire independently reproduced the core finding.
Sign in to Grok Bot for Windows 0.16.0.
Instruct the agent to use its graphical Chrome browser to open https://httpbingo.org/user-agent.
Prohibit terminal commands, curl, Python and other HTTP clients.
Observe the returned User-Agent header. Confirm the suffix follows GrokAgent/1.0 (u:<16 hexadecimal characters>).
Refresh or open the endpoint in another tab to check whether the value remains stable. Redact the complete identifier before publishing screenshots.
File hashes
sha256:955fb24e72ec85729cac2f921758a93a85089a0fc659e712125d6650b364d20e app(2).asar
Company response
RuntimeWire requested comment; the company had not responded by publication time.
SpaceXAI 的 Grok Bot 通过嵌入在 Chrome 的 user-agent 头中的持久标签识别其云浏览器背后的账户，RuntimeWire 发现。
在 2026 年 8 月 12 日的一次实测中，一个已登录的 Windows 版本 Grok Bot 通过其图形化云浏览器打开了 Httpbingo 的 user-agent 端点。外部服务器收到了如下头部，账户标签由 RuntimeWire 部分脱敏：
GrokAgent/1.0 令牌标识发送请求的软件。紧随 u: 的值更进一步：它区分了正在操作该浏览器的已认证 Cursor (@Cursor) 账户。
该标签不包含客户的姓名、电子邮件地址、访问令牌或原始 Cursor 账户 ID。它是一个化名的、来源于账户的标识符，为网站提供了一种无需 Cookie 就能识别随后携带相同值的流量的方式。
RuntimeWire 测试了一个已认证的账户。该测试确认该功能在该账户上处于激活状态，并且该标识符已发送到一个无关的外部服务器。但这并不能确定 Grok Bot 在多大范围内启用了该行为。…
When you purchase through links in our articles, we may earn a small commission. This doesn’t affect our editorial independence.