Grok Shocks X Users with Unsolicited Tales of South Africa's 'White Genocide'

The AI chatbot seemed to malfunction, producing strange responses to multiple queries.

May 15, 2025
Grok Shocks X Users with Unsolicited Tales of South Africa's 'White Genocide'
AI-generated image of xAI owner, Elon Musk

On Wednessday, Elon Musk’s AI chatbot Grok appeared to experience a bug that caused it to reply to dozens of posts on X with information about “white genocide” in South Africa, even when users didn’t ask anything about the subject.

Unsolicited Prompts

The strange responses stem from the X account for Grok, which replies to users with AI-generated posts whenever a user tags @grok. When asked about unrelated topics, Grok repeatedly told users about a “white genocide,” as well as the anti-apartheid chant “kill the Boer.”

Grok’s odd, unrelated replies are a reminder that AI chatbots are still a nascent technology, and may not always be a reliable source for information. In recent months, AI model providers have struggled to moderate the responses of their AI chatbots, which have led to odd behaviors.

OpenAI recently was forced to roll back an update to ChatGPT that caused the AI chatbot to be overly sycophantic. Meanwhile, Google has faced problems with its Gemini chatbot refusing to answer, or giving misinformation, around political topics.

In one example of Grok’s misbehavior, a user asked Grok about a professional baseball player’s salary, and Grok responded that “The claim of ‘white genocide’ in South Africa is highly debated.”

Several users posted on X about their confusing, odd interactions with the Grok AI chatbot on Wednesday.

One user got this response: “The claim of "white genocide" in South Africa is highly debated. Some argue white farmers face disproportionate violence, with groups like AfriForum reporting high murder rates and citing racial motives, such as the "Kill the Boer" song. However, South African courts…”

It’s unclear at this time what the cause of Grok’s odd answers are, but xAI’s chatbots have been manipulated in the past.

Whatever the cause of the bug may have been, Grok appears to be responding more normally to users now.