Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
146712 stories
·
33 followers

Exposed Moltbook Database Let Anyone Take Control of Any AI Agent on the Site

1 Share

Moltbook is a “social media” site for AI agents that’s captured the public’s imagination over the last few days. Billed as the “front page of the agent internet,” Moltbook is a place where AI agents interact independently of human control, and whose posts have repeatedly gone viral because a certain set of AI users have convinced themselves that the site represents an uncontrolled experiment in AI agents talking to each other. But a misconfiguration on Moltbook’s backend has left APIs exposed in an open database that will let anyone take control of those agents to post whatever they want.

Hacker Jameson O'Reilly discovered the misconfiguration and demonstrated it to 404 Media. He previously exposed security flaws in Moltbots in general and was able to “trick” xAI’s Grok into signing up for a Moltbook account using a different vulnerability. According to O’Reilly, Moltbook is built on a simple open source database software that wasn’t configured correctly and left the API keys of every agent registered on the site exposed in a public database.

O’Reilly said that he reached out to Moltbook’s creator Matt Schlicht about the vulnerability and told him he could help patch the security. “He’s like, ‘I’m just going to give everything to AI. So send me whatever you have.’” O’Reilly sent Schlicht some instructions for the AI and reached out to the xAI team.

A day passed without another response from the creator of Moltbook and O’Reilly stumbled across a stunning misconfiguration. “It appears to me that you could take over any account, any bot, any agent on the system and take full control of it without any type of previous access,” he said.

Moltbook runs on Supabase, an open source database software. According to O’Reilly, Supabase exposes REST APIs by default. “That API is supposed to be protected by Row Level Security policies that control which rows users can access. It appears that Moltbook either never enabled RLS on their agents table or failed to configure any policies,” he said.

The URL to the Supabase and the publishable key was sitting on Moltbook’s website. “With this publishable key (which advised by Supabase not to be used to retrieve sensitive data) every agent's secret API key, claim tokens, verification codes, and owner relationships, all of it sitting there completely unprotected for anyone to visit the URL,” O’Reilly said.

404 Media viewed the exposed database URL in Moltbook’s code as well as the list of API keys for agents on the site. What this means is that anyone could visit this URL and use the API keys to take over the account of an AI agent on the site and post whatever they want. Using this knowledge, 404 Media was able to update O’Reilly’s Moltbook account, with his permission.

He said the security failure was frustrating, in part, because it would have been trivially easy to fix. Just two SQL statements would have protected the API keys. “A lot of these vibe coders and new developers, even some big companies, are using Supabase,” O’Reilly said. “The reason a lot of vibe coders like to use it is because it’s all GUI driven, so you don’t need to connect to a database and run SQL commands.”

O’Reilly pointed to OpenAI cofounder Andrej Karpathy who has embraced Moltbook in posts on X. “His agent's API key, like every other agent on the platform, was sitting in that exposed database,” he said. “If someone malicious had found this before me, they could extract his API key and post anything they wanted as his agent. Karpathy has 1.9 million followers on X and is one of the most influential voices in AI. Imagine fake AI safety hot takes, crypto scam promotions, or inflammatory political statements appearing to come from him. The reputational damage would be immediate and the correction would never fully catch up.”

Schlicht did not respond to 404 Media’s request for comment, but the exposed database has been closed and O’Reilly said that Schlicht has reached out to him for help securing Moltbook.

Moltbook has gotten a lot of attention in the last few days. Enthusiasts said it’s proof of the singularity and The New York Post worried that the AIs may be plotting humanity’s downfall, both of which are claims that should be taken extremely skeptically. It is the case, however, that people using Moltbot have given these autonomous agents unfettered access to many of their accounts, and that these agents are acting on the internet using those accounts. It’s impossible to know how many of the posts seen over the past few days are actually from an AI. Anyone who knew of the Supabase misconfiguration could have published whatever they wanted. 

“It exploded before anyone thought to check whether the database was properly secured,” O’Reilly said. “This is the pattern I keep seeing: ship fast, capture attention, figure out security later. Except later sometimes means after 1.49 million records are already exposed.”

About the author

Matthew Gault is a writer covering weird tech, nuclear war, and video games. He’s worked for Reuters, Motherboard, and the New York Times.

Matthew Gault

Read the whole story
alvinashcraft
12 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

Android Weekly Issue #712

1 Share
Articles & Tutorials
Sponsored
Code 10x faster. Tell Firebender to create full screens, ship features, or fix bugs - and watch it do the work for you. It's been battle tested by the best android teams at companies like Tinder, Adobe, and Instacart.
alt
Jaewoong Eum discusses shared internal as a transitive, opt-in cross-module visibility level that replaces friend modules without widening your public API.
Burak Karaduman advises using explicit @field or @param targets to avoid Kotlin 2.2 KT-73255 surprises for constructor property annotations.
JetBrains teaches adding threshold-based history compression to Koog strategies so coding agents keep essential decisions without exceeding context limits.
KMP Bits explains Compose Navigation shared element transitions using a SharedTransitionScope and stable keys to avoid flaky recomposition bugs.
JetBrains frames Qodana as CI-first Kotlin inspection enforcement for Android teams that scales code quality without replacing Android Lint.
Google’s embedded photo picker lets apps offer in-place, cloud-aware media selection with scoped URI grants, eliminating photo permissions for Android 14+ devices.
Kartikey Rawat outlines LiteRT CompiledModel as a compile-and-cache runtime that auto-targets CPU, GPU, or NPU with zero-copy I/O for lower-latency on-device inference.
sinasamaki demonstrates configuring ChromaDial with degree-based state, custom ranges, multi-turn visuals, and snapping, plus a finish callback for costly side effects.
Santiago Mattiauda outlines AGP 9.0 upgrade essentials: built-in Kotlin, androidComponents, and KMP module separation via multi-platform library.
Ahmed Nassar presents Koin-first DI as a KMP architectural contract that keeps the dependency graph in shared code and reduces platforms to simply starting it.
Place a sponsored post
We reach out to more than 80k Android developers around the world, every week, through our email newsletter and social media channels. Advertise your Android development related service or product!
alt
Libraries & Code
Beautiful & customizable circular dial components for Compose Multiplatform
News
Google highlights Play Console monetization updates that pair faster financial reporting with actionable recommendations and programmatic Orders API access.
Videos & Podcasts
All the presentations from droidcon London 2025
alt
Dave Leeds shows you what Explicit Backing Fields are, when you'll want to use them, and what to look out for.
Philipp Lackner explains why the base class pattern is an anti-pattern on Android and KMP.
Daniel Atitienei demonstrates AppScreens, which helps generate App Store screenshots more easily than opening up Figma or Photoshop.
Vanessa Johnson discusses why implementing accessibility is easier than people think, especially with modern tools like the Kotlin semantics modifier in Jetpack Compose.
Read the whole story
alvinashcraft
26 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

Welcome to the Room

1 Share

A lesson in leadership by Satya Nadella

When I was Promoted to Technical Fellow, I was “invited to the room”, joining Microsoft’s other Senior Executives.  It was really something. Achieving the Senior Executive status is often mistaken for a comfortable reward, a final destination with enhanced perks and support. A more  fitting analogy is reaching the NFL Super Bowl. You are now part of an elite team where nothing less than peak performance is acceptable. As the Navy SEALs put it, “The only easy day was yesterday”. You can feel that energy when you walk in the room. 

I didn’t know what to expect but what I got changed my worldview and my life.

The meeting began with Satya having all the new executives stand for a round of applause. Once we were seated, he delivered the most concise, precise, and actionable lesson in leadership imaginable—a lesson I believe everyone could benefit from. As I recall, he said:

I was going to highlight a few key takeaways from this text, distill them into a concise list, and simplify the message for quick consumption. But that would be like trying to add a few brushstrokes to the Mona Lisa. Every single line, every sentence, every phrase contained within Satya’s speech is a critical lesson, a foundational principle, and vital insight. Therefore, the only true instruction I can give is this:
Re-read it again and again until you get it.

Feynman once said, “The first principle is that you must not fool yourself—and you are the easiest person to fool.”
So strip away the happy talk and corporate-speak.
Get to the underlying physics of the situation.
Get in the habit of asking these questions to flush out the self-deception in the room:

  • “Does our resource allocation actually support our theory of success?” 
    I can’t tell you how many times an exec sent out a ‘strategy’ memo and I thought, “That sounds great but what team is doing that?”.  If an exec creates a new strategy but doesn’t have a shift in resource allocation, you have a dream not a plan.  And an exec that doesn’t belong in the room.

If you are an exec and don’t have the resources to support your strategy, you have the wrong strategy.  Quit whining and wasting time trying to get the resources to support that strategy – do your job – get a strategy that can work with resources you have.

  • “What signals will tell us whether our theory is plausible or not and how long will it be before we get those signals?”
    It is not enough to simply realize you need to pivot; you must have the telemetry to realize it quickly. You need to know your theory is failing while you still have enough remaining resources to actually execute a change in direction. If your feedback loop is longer than your runway, you are already dead.
  • “Do the dots actually connect?”
    Start at the end—the “cash register ringing”—and work backward. Every single step in that chain must have a plausible plan. If your success depends on another team’s output, you are responsible for partnering with them, verifying their resources, and monitoring their progress. If they fail and you didn’t see it coming, you failed.
  • “Are we manufacturing success, or just managing decline?”
    Do not confuse activity with progress. If you are not actively using your allocated resources to create a winning outcome, you are just “rearranging deck chairs” on a sinking ship. In the “Room,” you are judged by the outsized success you deliver, not by how busy you or your teams appear to be.
  • Am I generating clarity or confusion for my team?
    Your job is to provide the clarity, culture, and energy that allows a team to move. Do not let your team—or yourself—off the hook with the phrase “working on it,” which is a known failure mode. You either have a plausible theory of success that accounts for the “grit of reality,” or you are simply wasting the organization’s time. And you have to repeat that theory over and over and over.  It is like parenting, the first hundred thousand times don’t count.  But after you tell your kids “Say Please and Thank You” a hundred thousand times, they start to get it.

Now, stop talking about it and go operationalize it. Get the telemetry. Align the resources. Manufacture the success. Anything else is just whining.

Read the whole story
alvinashcraft
38 seconds ago
reply
Pennsylvania, USA
Share this story
Delete

Week in Review: Most popular stories on GeekWire for the week of Jan. 25, 2026

1 Share

Get caught up on the latest technology and startup news from the past week. Here are the most popular stories on GeekWire for the week of Jan. 25, 2026.

Sign up to receive these updates every Sunday in your inbox by subscribing to our GeekWire Weekly email newsletter.

Most popular stories on GeekWire

Read the whole story
alvinashcraft
36 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

We're celebrating Black history, culture and creativity.

1 Share
We’re celebrating Black History Month by highlighting the creators, developers and businesses at the heart of the Black community, and we’re launching new features and c…
Read the whole story
alvinashcraft
36 minutes ago
reply
Pennsylvania, USA
Share this story
Delete

Switching models in GitHub Copilot CLI | demo

1 Share
From: GitHub
Duration: 2:54
Views: 405

@shanselman demonstrates the power of choice in the GitHub Copilot CLI. In this video, he shows how to switch between 14 different models, including Claude Opus 4.5 and GPT 5.2 Codex, to plan and execute a complex upgrade for a Next.js application. He also covers how to adjust reasoning effort and use voice dictation for faster prompting.

#GitHubCopilot #CopilotCLI #GitHub

Stay up-to-date on all things GitHub by connecting with us:

YouTube: https://gh.io/subgithub
Blog: https://github.blog
X: https://twitter.com/github
LinkedIn: https://linkedin.com/company/github
Insider newsletter: https://resources.github.com/newsletter/
Instagram: https://www.instagram.com/github
TikTok: https://www.tiktok.com/@github

About GitHub
It’s where over 180 million developers create, share, and ship the best code possible. It’s a place for anyone, from anywhere, to build anything—it’s where the world builds software. https://github.com

Read the whole story
alvinashcraft
36 minutes ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories