WormGPT Reports: History, Claims and Business Email Defence

WormGPT is a name used in reports about services marketed for malicious AI use. Reports about the original 2023 offering and later similarly branded variants describe different evidence and periods. Defenders should focus on the resulting fraud attempt, account access and payment approval process.

Jan 04, 2025 - 14:47
Updated: 
129.3k

AI in Cybersecurity in Cybersecurity & Ethical Hacking · Tutorial

Cyber Threats, Scams & Online Safety

WormGPT Reports: History, Claims and Business Email Defence

Quick answer: WormGPT is a name used in reports about services marketed for malicious AI use. Reports about the original 2023 offering and later similarly branded variants describe different evidence and periods. Defenders should focus on the resulting fraud attempt, account access and payment approval process. Verify unusual instructions through an established channel, strengthen account authentication, and investigate suspicious messages without visiting criminal services or assuming polished writing proves AI use.

Key takeaways

  • Attribute product and model claims to dated research.
  • Do not treat every WormGPT-branded service as the same system.
  • Review payment changes through an independent established channel.
  • Use email authentication alongside account and transaction controls.
  • Preserve evidence and respond to the observed activity.

Table of Contents

What do the dated WormGPT reports actually establish?

Cato CTRL research published on 17 June 2025 describes the original WormGPT appearing publicly in June 2023 and shutting down in August 2023. It also reports later services using the name and attributes particular variants to underlying model services through its own investigation.

Palo Alto Networks Unit 42 research examines malicious LLM offerings and their claims. Keep those observations attributed to the researchers. A seller's advertisement is not an independently verified capability, and a historical report does not establish that a named service is available or unchanged today. For a defender's incident report, separate what a message did from an unproven claim about which AI system wrote it.

Why is the payment request more useful than the writing style?

In an illustrative case, accounts clerk Neha receives a fluent message in an existing supplier thread. It asks her to replace the supplier's bank details before an urgent invoice payment. There are no spelling errors. The unusual requested action and changed financial destination require review regardless of who or what composed the text.

The FBI business email compromise guidance recommends verifying payment changes through established contact methods. Neha uses a number already held in the supplier record, not a new number from the message. She records who confirmed the request and follows the organisation's approval process. An independent contact can reveal a mismatch, but a callback by itself does not prove the entire supplier account or internal approval chain is secure.

Message featureWhat it tells NehaAction
Fluent writingThe text is readableDo not infer legitimacy or AI authorship
Changed bank detailsA consequential account change is requestedUse independent verification
Urgent deadlineThe sender wants a quick decisionKeep ordinary approval requirements
Existing message threadPrior context is presentCheck for account compromise as well

What can DMARC help with, and where does it stop?

Microsoft DMARC guidance explains domain-based email authentication using alignment with SPF or DKIM results and a published policy. Correct deployment can help receivers handle unauthorised use of a protected domain. Review legitimate senders before enforcing a restrictive policy so expected business mail is not disrupted.

A message from a lookalike domain or a genuinely compromised mailbox can present a different problem. Passing authentication does not approve an invoice, validate a new bank account or prove the person controlling the mailbox is authorised to make that change. Neha's team keeps domain authentication, mailbox security and financial approval as separate controls. Each closes a different path in the fictional payment request.

Which account protections matter beyond message filtering?

Review authentication for mailboxes and finance applications, particularly accounts that can approve payments or change supplier records. NIST SP 800-63B-4 distinguishes phishing-resistant authentication from methods that can still be relayed or entered into a fraudulent site. An ordinary one-time code should not be described as phishing resistant merely because it adds a second factor.

Protect recovery paths and review unexpected access or consent changes as well. A stolen session may remain useful even after a password change, depending on the service and response actions. In Neha's case, the response team checks the relevant account sessions and rules under its approved procedures. The finance team continues to hold the payment while the account investigation proceeds.

How can staff practise the decision without generating a phish?

Use a clearly labelled paper exercise with an invented supplier and no live payment details. Give the participant the normal supplier record, the proposed change and an approval policy. Ask which established contact should be used and what evidence must be recorded before the change can proceed.

Include a second variation in which the supplier confirms a change but the internal approver is unavailable. The correct next step comes from the documented approval process, not the apparent urgency. Neha writes an exception request rather than inventing authority. Score the exercise on the decision and evidence collected, not on whether someone recognises a particular writing style. Avoid sending deceptive messages to real staff without a separately approved training plan.

Illustrative variationExpected decisionEvidence to keep
Unverified bank changeHold the changeEstablished contact used for verification
Verified supplier, missing internal approvalFollow the exception processNamed authorised decision maker
Possible mailbox compromiseEscalate for account investigationMessage and relevant account records
Payment already sentContact the financial institution promptlyTransaction reference and incident timeline

What should happen when the organisation receives a suspicious request?

Preserve the message and relevant metadata through the approved reporting channel. If a transfer has already occurred, contact the financial institution promptly and follow the applicable reporting process. Involve the team responsible for mailbox access, supplier records and financial approvals so the response covers more than the email itself.

NIST incident response guidance supports coordinated preparation, response and recovery. Neha's incident record contains the requested change, actions taken, people contacted and unresolved questions. The team avoids forwarding sensitive material widely or using a suspected message's own links for verification. It checks whether any supplier-record or payment-system changes were made and documents what was restored or left under review.

How should an analyst describe possible AI involvement?

State the observable behaviour first: an unauthorised bank-detail request, a compromised account indicator or a fraudulent destination. Record source and confidence separately when discussing AI involvement. A screenshot bearing a product name is not proof that the service generated the message or that the provider's advertised model was used.

Neha's final case note therefore describes attempted payment diversion and the interrupted approval step. It leaves authorship unconfirmed. That wording helps reviewers improve the process even when attribution remains uncertain. Read dated research to understand possible capabilities, but build detection and training around actions the organisation can observe and controls it can check without accessing a malicious service.

Related reading: PoisonGPT research and supply chain checks; transaction security for online shops.

References

Frequently Asked Questions

Defensive learning does not require contacting criminal services; use primary research and approved synthetic exercises without submitting credentials or business data.

Later reports describe similarly branded variants, so keep their dates, sources and observed capabilities separate from the original 2023 offering.

Readable writing establishes neither AI authorship nor legitimacy, so examine the requested action, destination and account evidence instead of style.

DMARC addresses particular domain-authentication problems, while lookalike domains and compromised legitimate accounts still require account and transaction controls.

Some methods can still be relayed through fraudulent sites, so check whether the chosen authenticator meets the relevant phishing-resistance requirements.

Verify the request through an established independent contact and follow the documented internal approval process before changing the supplier record.

Contact the financial institution promptly, preserve transaction details and involve the responsible incident and finance teams through approved reporting channels.

Describe the observed activity and label uncertain attribution clearly, because a service advertisement or writing style does not establish authorship.

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 2
Funny Funny 1
Wow Wow 0
Sad Sad 0
Angry Angry 1
Vaishnavi

Vaishnavi is a skilled tech professional at the Ethical Hacking Training Institute in Pune, responsible for managing and optimizing the technical infrastructure that supports advanced cybersecurity education. With deep expertise in network security, backend operations, and system performance, she ensures that practical labs, online modules, and assessments run smoothly and securely. Her behind-the-scenes contributions play a vital role in delivering a seamless and secure learning experience for aspiring ethical hackers.