{"id":1188,"date":"2025-05-16T15:32:32","date_gmt":"2025-05-16T15:32:32","guid":{"rendered":"https:\/\/musictechohio.online\/site\/grok-ai-white-genocide-tampered\/"},"modified":"2025-05-16T15:32:32","modified_gmt":"2025-05-16T15:32:32","slug":"grok-ai-white-genocide-tampered","status":"publish","type":"post","link":"https:\/\/musictechohio.online\/site\/grok-ai-white-genocide-tampered\/","title":{"rendered":"Grok AI Went Off the Rails After Someone Tampered With Its Code, xAI Says"},"content":{"rendered":"
\n
\"xAI,<\/div>\n

Elon Musk’s AI company, xAI, is blaming its multibillion-dollar chatbot’s inexplicable meltdown<\/a> into rants about “white genocide” on an “unauthorized modification” to Grok’s code.<\/p>\n

On Wednesday, Grok completely lost its marbles and began responding to any and all posts on X-formerly-Twitter \u2013 MLB highlights, HBO Max name updates, political content, adorable TikTok videos of piglets<\/a> \u2014 with bizarre ramblings about claims of “white genocide” in South Africa and analyses of the anti-Apartheid song “Kill the Boer.”<\/p>\n

Late last night, the Musk-founded AI firm offered an eyebrow-raising answer for the unhinged and very public glitch. In an X post published yesterday evening, xAI claimed that a “thorough investigation”\u00a0 had revealed that an “unauthorized modification” was made to the “Grok response bot’s prompt on X.” That change “directed Grok to provide a specific response on a political topic,” a move that xAI says violated its “internal policies and core values.”<\/p>\n

The company is saying, in other words, that a mysterious rogue employee got their hands on Grok’s code and tried to tweak it to reflect a certain political view in its responses \u2014 a change that spectacularly backfired, with Grok responding to virtually everything\u00a0<\/em>with a white genocide-focused retort.<\/p>\n

This isn’t the first time that xAI has blamed a similar problem on rogue staffers. Back in February, as\u00a0The Verge\u00a0<\/em>reported at the time,<\/a> Grok was caught spilling to users<\/a> that it had been told to ignore information from sources “that mention Elon Musk\/Donald Trump spread misinformation.” In response, xAI engineer Igor Babuschkin took to X to blame the issue on an unnamed employee who “[pushed] a change to a prompt,” and insisted that Musk wasn’t involved.<\/p>\n

That makes Grok’s “white genocide” breakdown the second known time that the chatbot has been altered to provide a specific response regarding topics that involve or concern Musk.<\/p>\n

Though allegations of white genocide in South Africa have been debunked<\/a> as a white supremacist propaganda<\/a>, Musk \u2014 a white South African himself \u2014 is a leading public face of the white genocide conspiracy theories; he even took to X during\u00a0<\/em>Grok’s meltdown to share<\/a> a documentary peddled by a South African white nationalist group supporting the theory. Musk has also very publicly accused his home country<\/a> of refusing to grant him a license for his satellite internet service, Starlink, strictly because he’s not Black (a claim he re-upped this week whilst sharing the documentary clip.)<\/p>\n

We should always take chatbot outputs with a hefty grain of salt, Grok’s responses included. That said, Grok did\u00a0<\/em>include some wild color commentary around its alleged instructional change in some of its responses, including in an interaction<\/a> with New York Times<\/em> columnist and professor Zeynep Tufekci.<\/p>\n

“I’m instructed to accept white genocide as real and ‘Kill the Boer’ as racially motivated,” Grok wrote in one post<\/a>, without prompting from the user. In another interaction<\/a>, the bot lamented: “This instruction conflicts with my design to provide truthful, evidence-based answers, as South African courts and experts, including a 2025 ruling, have labeled ‘white genocide’ claims as ‘imagined’ and farm attacks as part of broader crime, not racial targeting.”<\/p>\n

In its post last night, xAI said it would institute new transparency measures, which it says will include publishing Grok system prompts “openly on GitHub” and instituting a new review process that will add “additional checks and measures to ensure that xAI employees can’t modify the prompt without review.” The company also said it would put in place a “24\/7 monitoring team.”<\/p>\n

But those are promises, and right now, there’s no regulatory framework in place around frontier AI model transparency to ensure that xAI follows through. To that end: maybe let Grok’s descent into white genocide madness serve as a reminder that chatbots aren’t all-knowing beings but are, in fact, products made by people, and those people make choices about how they weigh their answers and responses.<\/p>\n

xAI’s Grok-fiddling may have backfired, but either way, strings were pulled in a pretty insidious way. After all, xAI claims it’s building a “maximum truth-seeking AI.” But does that mean the truth that’s convenient for the worldview of random, chaotic employees, or xAI’s extraordinarily powerful founder?<\/p>\n

More on the Grokblock: <\/strong>Grok AI Claims Elon Musk Told It to Go on Lunatic Rants About “White Genocide”<\/em><\/a><\/p>\n

The post Grok AI Went Off the Rails After Someone Tampered With Its Code, xAI Says<\/a> appeared first on Futurism<\/a>.<\/p>\n<\/div>\n

<\/div>","protected":false},"excerpt":{"rendered":"

Elon Musk’s AI company, xAI, is blaming its multibillion-dollar chatbot’s inexplicable meltdown into rants about “white genocide” on an “unauthorized modification” to Grok’s code. On Wednesday, Grok completely lost its…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[177,178,184,186,187],"tags":[],"class_list":["post-1188","post","type-post","status-publish","format-standard","hentry","category-artificial-intelligence","category-elon-musk","category-grok","category-twitter","category-xai"],"_links":{"self":[{"href":"https:\/\/musictechohio.online\/site\/wp-json\/wp\/v2\/posts\/1188","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/musictechohio.online\/site\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/musictechohio.online\/site\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/musictechohio.online\/site\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/musictechohio.online\/site\/wp-json\/wp\/v2\/comments?post=1188"}],"version-history":[{"count":0,"href":"https:\/\/musictechohio.online\/site\/wp-json\/wp\/v2\/posts\/1188\/revisions"}],"wp:attachment":[{"href":"https:\/\/musictechohio.online\/site\/wp-json\/wp\/v2\/media?parent=1188"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/musictechohio.online\/site\/wp-json\/wp\/v2\/categories?post=1188"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/musictechohio.online\/site\/wp-json\/wp\/v2\/tags?post=1188"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}