Evidence over alarm
← Back to the incident library
Malicious useCASE STUDY / OpenAI

A fake support request targeted OpenAI staff

SweetSpecter sent fake support emails to OpenAI staff. OpenAI later linked the campaign’s infrastructure to ChatGPT accounts seeking technical help.

Source: OpenAI
ACTIVITYMay 2024
PUBLICLY DISCLOSEDMay 16, 2024
THE AI’S ROLEAI assists research; people run the attack

Proofpoint disclosed the campaign on May 16. OpenAI’s October 9 report later identified its involvement and the actor’s use of ChatGPT.

THE 10-SECOND TAKEAWAY

A blocked attempt can teach us which boundary mattered.

HOW IT WORKED

Follow the chain.

An explanation, not a technical reproduction.
Sender
→
Support request
→
Staff member
SIMPLIFIED VIEW · 1 / 3
STEP 01

A familiar-looking request

A help request carried an attachment with a hidden purpose.

Proofpoint Threat Research
Move through the story at your own pace.
1 / 3
THINK OF IT THIS WAY

An illustration: a visitor asks a receptionist to inspect a parcel that contains a hidden recording device. Checking it before delivery can interrupt the plan.

An analogy for the mechanism; not an additional claim about the incident.
KEEP THE EVIDENCE IN VIEW

What we know.
What we don’t.

Reported outcomes

OpenAI says its defenses blocked the malicious emails before they reached corporate inboxes. OpenAI

Important limits

The AI helped with supporting tasks; the report does not establish that it wrote the phishing emails.

Targeting is not successful access. This record covers the May campaign, not every operation attributed to SweetSpecter.

WHY IT MATTERS

The lesson beyond
this one case.

Security has to evaluate the request and what it brings with it. A convincing story does not establish permission to run an attachment.

What happened in response? +

OpenAI banned associated accounts and contacted targeted staff. OpenAI

FROM THE INCIDENT TO THE DEFENSE

What could help
an organization?

Editorial defense connection: protect communication channels and turn suspicious messages into a coordinated response.

Security operations

Connect detection to response

Combine email, endpoint and identity evidence so responders can investigate a reported message and contain any related activity.

What this does—and does not—establish

This is a general capability connection, not proof that a particular product would reproduce the reported outcome.

Employees

Protect the person behind the request

Give staff a trusted channel to verify unusual requests and report suspicious attachments, alongside technical email controls.

What this does—and does not—establish

The employee framework’s AI-use controls are only indirectly relevant here. The victim cannot govern the outside attacker’s AI accounts.

Editorial connections to relevant controls, not evidence that a particular technology would have prevented this case. Each guide links to the security guidance behind its recommendations.

Explore the full AI security framework
TRACE IT TO THE SOURCE

Read the evidence.

Explore more original accounts in the source report library ↗.

These are source-reported findings. An independent assessment, when available, is labeled explicitly.

01
Influence and cyber operations: an update, October 2024OpenAI · Oct 9, 2024 · provider and affected party investigation
02
Security Brief: Artificial Sweetener — SugarGh0st RAT Used to Target American Artificial Intelligence ExpertsProofpoint Threat Research · May 16, 2024 · primary campaign investigation

Read this case’s update history →

Reviewed Sep 11, 2026 · Editorial methodology · Structured data