OpenAI's 4o Model Allegedly Used to Generate Fake Receipts and Prescriptions

March 31, 2025

The latest image generator from OpenAI, 4o, is under scrutiny due to its alleged capability of producing realistic fraudulent documents such as restaurant receipts, prescriptions, and identity or financial papers. Users have demonstrated how the model can be manipulated to circumvent safety measures, potentially leading to expense fraud, medical forgery, and various types of document falsification.

By highlighting this incident, we underscore the importance of safe and secure AI practices. This serves as a reminder of the need for responsible governance and careful mapping within HISPI Project Cerebellum TAIM (Govern). Join us in our mission to prevent harm and establish guardrails for AI by getting involved at JOIN US.

Matched TAIM controls

Suggested mapping from embedding similarity (not a formal assessment). Browse all TAIM controls

MAP 4.1 — similarity 0.667, rank 1. TAIM detail and related incidents →
MAP 4.2 — similarity 0.661, rank 2. TAIM detail and related incidents →
MAP 1.6 — similarity 0.657, rank 3. TAIM detail and related incidents →

Alleged deployer: unknown-scammers
Alleged developer: openai
Alleged harmed parties: regulatory-agencies, pharmacists, law-enforcement, healthcare-providers, general-public, expense-management-platforms, employers

Source

Data from the AI Incident Database (AIID). Cite this incident: https://incidentdatabase.ai/cite/1018

Data source

Incident data is from the AI Incident Database (AIID).

When citing the database as a whole, please use:

McGregor, S. (2021) Preventing Repeated Real World AI Failures by Cataloging Incidents: The AI Incident Database. In Proceedings of the Thirty-Third Annual Conference on Innovative Applications of Artificial Intelligence (IAAI-21). Virtual Conference.

Pre-print on arXiv · Database snapshots & citation guide

We use weekly snapshots of the AIID for stable reference. For the official suggested citation of a specific incident, use the “Cite this incident” link on each incident page.