<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Grok-Bot on Martin&#39;s Blog</title>
		<link>https://mac.sploit.dk/tags/grok-bot/</link>
		<description>Recent content in Grok-Bot on Martin&#39;s Blog</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://mac.sploit.dk/tags/grok-bot/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Grok Bot: All Your Creds Are Belong to the Cloud</title>
				<link>https://mac.sploit.dk/blog/grok-bot-all-your-creds/</link>
				<pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://mac.sploit.dk/blog/grok-bot-all-your-creds/</guid>
				<description>&lt;p&gt;Grok Bot connects an AI agent to a computer and external services such as Gmail&#xA;and Notion. You install the desktop app, connect your accounts through a browser,&#xA;and let the agent work. I wanted to understand where those credentials go and&#xA;what someone could do with the desktop app&amp;rsquo;s own token.&lt;/p&gt;&#xA;&lt;p&gt;I unpacked the Linux application, version 0.71.2, traced its authentication and&#xA;connector code, and tested the saved access token against the backend. The&#xA;interesting boundary is between the desktop session and the cloud services that&#xA;act on your behalf.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
