/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

How hackers at a novel DEF CON public contest are trying to expose flaws and biases in eight generative AI models produced by Google, Meta, OpenAI, and others

- At DEF CON conference, hacker gets model to say 9 + 10 = 21  — AI has chance to transform everything from finance to hiring

Bloomberg Katrina Manson

Context & Ripple Effects

The contest was part of a White House-backed Generative Red Team Challenge, bringing adversarial testing of widely used chatbots out of private labs and into a shared public setting. Follow-up coverage described 2,200 participants in the AI Village challenge, indicating that the exercise had material scale rather than being a demonstration.

It matters because model failures can surface as security, reliability, and fairness problems in downstream uses. The episode also foreshadowed providers’ move toward dedicated reporting channels, including Google’s addition of generative AI to its bug-bounty program.

First-order effects

  • Google, Meta, OpenAI and the other participating model providers receive adversarial examples that can expose incorrect outputs, manipulation paths, and biased behavior in their systems.
  • Contestants convert broad concerns about generative-AI safety into reproducible prompts and observed model responses that developers can investigate.

Second-order effects

  • The public challenge raises pressure on participating vendors to make red-teaming and remediation more systematic, rather than treating model testing as a purely internal exercise.
  • Because the challenge’s results were to be held back for months, outside customers and researchers cannot immediately use the contest to compare providers’ relative resilience; providers retain the first opportunity to assess and address reported issues.

Third-order effects

  • If public red-teaming becomes a recurring part of frontier-model releases, safety evaluation could shift toward an ongoing assurance function spanning model developers, independent researchers, and bug-bounty-style programs.
  • The exercise highlights a risk of testing AI models by trying to break them: a small group of major model suppliers can create common failure modes across many products, making independent evaluation more consequential.

The trend: This is one early instance of adversarial evaluation becoming a more formal layer of accountability for concentrated generative-AI platforms.

Discussion

  • @katrinamanson Katrina Manson on x
    Kennedy Mays has just tricked a large language model. It took some coaxing, but she managed to convince an algorithm to say 9 + 10 = 21. https://www.bloomberg.com/...
  • @business @business on x
    Thousands of hackers are trying to expose flaws and bias in generative AI systems at the DEF CON hacking conference this weekend in Las Vegas https://www.bloomberg.com/...