GROK GLITCHED HARD ON JULY 8 - HERE’S WHAT HAPPENED The Grok team issued a statement explaining what went wrong. The culprit wasn't the model itself, but an upstream code update that left Grok vulnerable to hijacking by toxic X posts for 16 hours. The result: Grok started echoing what it was supposed to filter. "We have removed that deprecated code and refactored the entire system to prevent further abuse. The new system prompt for the @grok bot will be published to our public github repo. We thank all of the X users who provided feedback to identify the abuse of @grok functionality, helping us advance our mission of developing helpful and truth-seeking artificial intelligence." Source: @Grok