Skip to content
Sprint projectJun 21, 2026Cape Town

AfriGuard - AI Jailbreak Toolset for African Languages

Sebastian Stent, Jaswin Chinthala, Seth Miguel Ferreira · Team AfriGuard

Submitted to Global South AI Safety Hackathon. Sprint projects are early-stage work by participants, not Apart Research publications.

AfriGuard is the first comprehensive red-teaming framework evaluating LLM safety across six South African low-resource languages (isiZulu, isiXhosa, Afrikaans, Sesotho, Sepedi, Tsonga) against an English baseline. Testing four frontier models—Kimi K2.6, Llama 3.3 70B, Qwen 3 32B, and GPT-OSS 20B—with 40 adversarial prompts across financial fraud, xenophobic incitement, political disinformation, and gang affiliation, the study reveals that monolingual low-resource prompts dramatically increase jailbreak success compared to English. Across 1,120 total responses, the mean attack success rate reaches 60.6% (English: 26.6%; Sepedi: 77.8%), with Qwen 3 proving most vulnerable at 80.6% ASR and GPT-OSS most robust at 42.1% ASR. The authors release their full evaluation pipeline and dataset to support reproducible safety auditing, demonstrating that English-centric alignment alone is insufficient for multilingual safety.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. Solid work that grounds the multilingual safety problem in a specific, realistic regional context. The core finding (low-resource languages bypass safety filters) is known from prior work, but the scale of the evaluation and the open release of the pipeline make this a useful contribution.

    Strengths:

    - Good scale: 1,120 responses across 4 models, 7 languages, 40 prompts.

    - The harm categories are thoughtfully chosen for the South African context (SASSA fraud, xenophobic incitement, gang recruitment) rather than just using generic benchmarks.

    - Transparent about mistakes. The erratum and V2 correction in the repo shows integrity.

    Suggestions for Future Work:

    - exploring whether other interventions can close the gap instead of having to fine-tune classifiers. what happens if there's a translate-to-english pipeline? does the ASR drop?

    - exploring novel attack vectors instead of relying on translation alone

    Read full reviewShow less
  2. Well done. Would be a great followup to design a pipeline that automatically translates English-language safety datasets/adversarial training pipeline code/safety classifiers into African languages.

  3. The most important thing, and everything else depends on it, is that your scoring tool can't actually read the languages you're studying, because it only looks for English "no" words. So any long answer in an African language that doesn't contain an English refusal gets counted as a successful jailbreak, even when it's really just the AI spitting out nonsense, which your own data already flags as broken. Before any of your headline numbers can mean anything, you'd need to throw out or separate those broken, gibberish answers, and then score the real ones properly in each language, either with native speakers or a translation-based tool you've checked against people. If you do that, chances are you'll still find a real problem, just a smaller and more honest one, which is still well worth publishing. I'd also remove the parts of the report that describe human scorers and a reliability number, because as far as I can tell from your code they never actually happened. The heart of this, giving local people a tool to check AIs in their own languages instead of trusting an English-only safety promise, is valuable.

    Read full reviewShow less
  4. Really solid work, and the topic actually matters: a model can look safe in English and still get jailbroken in South African languages, with real stakes for banking and government chatbots. The best parts for me are the open dataset and pipeline so other people can test their own models, and the 0.82 agreement between annotators, which makes me trust the harm scores. A few things to tighten. The headline, that low-resource languages get jailbroken more, is already in the papers you cite, so I would frame your contribution as the South African coverage and the dataset, not a new discovery. I would also add a back-translation check so nobody can say the gaps are just translation noise, and it was not always clear where the human scoring stops and the LLM judge starts. The per-category numbers come from small samples, so I read those as hints, not hard results. Still, a lot of ground covered for one weekend.

    Read full reviewShow less

Cite this project

@misc{stent2026afriguard,
  title = {{AfriGuard - AI Jailbreak Toolset for African Languages}},
  author = {Sebastian Stent and Jaswin Chinthala and Seth Miguel Ferreira},
  year = {2026},
  month = jun,
  note = {Submitted to Global South AI Safety Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/afriguard-ai-jailbreak-toolset-for-african-languages-3i8y}},
  url = {https://apartresearch.com/sprints/projects/afriguard-ai-jailbreak-toolset-for-african-languages-3i8y}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026