Skip to content
Sprint projectJan 11, 2026Germany

Detecting Adversarial Prompts in Business Context

Joshua Kehrer · Team Joshua Kehrer & Joshua Quenzer-Hohmuth

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

Read the report

Report: Detecting Adversarial Prompts in Business Context

Code (opens in new tab)
Share

This work examines how strategically framed user inputs can manipulate AI systems in organizational settings. It investigates whether such manipulation-inducing inputs can be detected before model execution through a lightweight pre-processing layer. The study frames input filtering as a risk-management and governance challenge rather than a purely technical fix.

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. Shifting the focus from technical jailbreaks to 'business context' manipulation (like urgency or authority framing) is a smart, novel approach. While the initial validation on ~38 samples serves as a good proof-of-concept for the hackathon, I would love to see this expanded to a larger dataset in future iterations to better support the generalization claims. Additionally, verifying the results against human-authored data (e.g., Enron or real phishing logs) would be a fantastic next step to mitigate the risk of circularity inherent in synthetic testing. Great concept that addresses a real gap.

    Excellent work overall!

Cite this project

@misc{kehrer2026detecting,
  title = {{Detecting Adversarial Prompts in Business Context}},
  author = {Joshua Kehrer},
  year = {2026},
  month = jan,
  note = {Submitted to AI Manipulation Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/detecting-adversarial-prompts-in-business-context-wv35}},
  url = {https://apartresearch.com/sprints/projects/detecting-adversarial-prompts-in-business-context-wv35}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026