A Cofense tracked phishing email poses as a ChatGPT billing “final notice,” demands $23.80 within 48 hours, and sends victims to a fake OpenAI login page that captures credentials. The payment button routes through notifications.googleapis.com before reaching attacker controlled infrastructure, showing why a familia...
Published byEdited with GPT-5.6 TerraImages generated with GPT Image 2
Research answer

Create a landscape editorial hero image for this Studio Global article: What are the details of the phishing campaign reported by Cofense that uses fake OpenAI subscription-invoice emails to target both enterpris. Article summary: Cofense identified a credential-phishing campaign that impersonates OpenAI/ChatGPT billing to target both work and personal users. It combines a small, urgent payment demand with convincing ChatGPT branding and a fake si. Topic tags: general, general web. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fake numbers, clic
A phishing campaign identified by Cofense’s Phishing Defense Center uses a convincing ChatGPT subscription notice to steal OpenAI account credentials from both workplace and personal users. Its formula is straightforward: a modest $23.80 charge, a 48-hour deadline, familiar ChatGPT branding, and a payment button that ultimately leads to a counterfeit sign-in page. 3
4
The observed message uses the subject line “Urgent: Update Your Payment Method to Avoid Service Interruption.” It claims that the recipient has an outstanding balance of $23.80 and must act within 48 hours to prevent disruption. 3
4
Visual cues make the email appear credible. Researchers reported that it includes the ChatGPT logo, a “final notice” presentation, urgent billing language, an “Update Payment Information” button, and a closing attributed to “The OpenAI Team.” 1
4
But the sending address is a decisive red flag: support@9527db6e1a.nxcli.io. That is not an OpenAI domain. 3
The payment button does not send recipients to an OpenAI billing page. Cofense traced the link through a notifications.googleapis.com redirect URL before it forwarded users to attacker-controlled infrastructure. 1
4
The final site mimics the ChatGPT login experience with familiar branding and interface elements. When a target enters an OpenAI username and password, the counterfeit page captures those credentials, then redirects the victim to an error page—an apparent attempt to make the failed process seem like a routine technical problem. 1
4
The use of a Google redirect wrapper is notable, but it does not make the link trustworthy. A recognizable domain can appear as one step in a redirect chain while the final destination is malicious. 1
4
Cofense reported that the campaign targets people using ChatGPT through work accounts as well as personal accounts. 1
3 A stolen OpenAI login may give an attacker access to whatever the affected account can access or contains, which can vary widely by user and organization.
For some users, that could include chat history, subscription and payment settings, API usage, API keys, prompts, uploaded files, or connected work processes. The practical impact depends on how the account is used and what data or systems are associated with it.
The campaign also reflects a broader phishing pattern: attackers borrow the branding of widely used technology products, including Microsoft, Google, and Adobe, then pair it with a time-sensitive account or billing problem to pressure recipients into acting before verifying the message. 1
3
This specific campaign offers several useful detection clues:
nxcli.io is not an OpenAI domain. notifications.googleapis.com rather than taking the recipient directly to an expected OpenAI destination. Do not click the payment button or reply to the message. Instead, open a browser yourself and visit auth.openai.com to check account access or billing status independently. 1
3
Before opening any link in a billing email, inspect the sender address and hover over the button or link to examine where it is intended to go. A familiar brand or intermediate redirect domain is not enough to establish that the final site is legitimate. 1
3
Security teams can investigate or block the observed sender and related redirect infrastructure. Cofense reporting identifies the nxcli.io payload paths /fertaq/app/login.php and /fertaq/app/key.php as relevant indicators from this campaign. 1
3
Treat credentials entered on the imitation page as compromised. Change the OpenAI password immediately using a directly opened, trusted OpenAI address. If the account uses API keys, rotate any keys that may have been exposed, review active sessions and recent account changes, and report the incident to the organization’s security team where applicable.
The essential lesson is simple: an urgent ChatGPT billing demand is not proof of a billing problem. Verify account issues from a separately opened official site—not through the link in the email.
Studio Global AI
This page includes a source-backed answer you can continue inside Studio Global.
A Cofense tracked phishing email poses as a ChatGPT billing “final notice,” demands $23.80 within 48 hours, and sends victims to a fake OpenAI login page that captures credentials.
A Cofense tracked phishing email poses as a ChatGPT billing “final notice,” demands $23.80 within 48 hours, and sends victims to a fake OpenAI login page that captures credentials. The payment button routes through notifications.googleapis.com before reaching attacker controlled infrastructure, showing why a familiar service in a link chain is not proof that the destination is safe.
Do not use the email link to resolve billing concerns. Open a browser independently, sign in through auth.openai.com, and reset credentials promptly if you submitted them to the suspected phishing page.
A Cofense tracked phishing email poses as a ChatGPT billing “final notice,” demands $23.80 within 48 hours, and sends victims to a fake OpenAI login page that captures credentials. The payment button routes through notifications.googleapis.com before reaching attacker controlled infrastructure, showing why a familia...
Published byEdited with GPT-5.6 TerraImages generated with GPT Image 2
Research answer

Create a landscape editorial hero image for this Studio Global article: What are the details of the phishing campaign reported by Cofense that uses fake OpenAI subscription-invoice emails to target both enterpris. Article summary: Cofense identified a credential-phishing campaign that impersonates OpenAI/ChatGPT billing to target both work and personal users. It combines a small, urgent payment demand with convincing ChatGPT branding and a fake si. Topic tags: general, general web. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fake numbers, clic
A phishing campaign identified by Cofense’s Phishing Defense Center uses a convincing ChatGPT subscription notice to steal OpenAI account credentials from both workplace and personal users. Its formula is straightforward: a modest $23.80 charge, a 48-hour deadline, familiar ChatGPT branding, and a payment button that ultimately leads to a counterfeit sign-in page. 3
4
The observed message uses the subject line “Urgent: Update Your Payment Method to Avoid Service Interruption.” It claims that the recipient has an outstanding balance of $23.80 and must act within 48 hours to prevent disruption. 3
4
Visual cues make the email appear credible. Researchers reported that it includes the ChatGPT logo, a “final notice” presentation, urgent billing language, an “Update Payment Information” button, and a closing attributed to “The OpenAI Team.” 1
4
But the sending address is a decisive red flag: support@9527db6e1a.nxcli.io. That is not an OpenAI domain. 3
The payment button does not send recipients to an OpenAI billing page. Cofense traced the link through a notifications.googleapis.com redirect URL before it forwarded users to attacker-controlled infrastructure. 1
4
The final site mimics the ChatGPT login experience with familiar branding and interface elements. When a target enters an OpenAI username and password, the counterfeit page captures those credentials, then redirects the victim to an error page—an apparent attempt to make the failed process seem like a routine technical problem. 1
4
The use of a Google redirect wrapper is notable, but it does not make the link trustworthy. A recognizable domain can appear as one step in a redirect chain while the final destination is malicious. 1
4
Cofense reported that the campaign targets people using ChatGPT through work accounts as well as personal accounts. 1
3 A stolen OpenAI login may give an attacker access to whatever the affected account can access or contains, which can vary widely by user and organization.
For some users, that could include chat history, subscription and payment settings, API usage, API keys, prompts, uploaded files, or connected work processes. The practical impact depends on how the account is used and what data or systems are associated with it.
The campaign also reflects a broader phishing pattern: attackers borrow the branding of widely used technology products, including Microsoft, Google, and Adobe, then pair it with a time-sensitive account or billing problem to pressure recipients into acting before verifying the message. 1
3
This specific campaign offers several useful detection clues:
nxcli.io is not an OpenAI domain. notifications.googleapis.com rather than taking the recipient directly to an expected OpenAI destination. Do not click the payment button or reply to the message. Instead, open a browser yourself and visit auth.openai.com to check account access or billing status independently. 1
3
Before opening any link in a billing email, inspect the sender address and hover over the button or link to examine where it is intended to go. A familiar brand or intermediate redirect domain is not enough to establish that the final site is legitimate. 1
3
Security teams can investigate or block the observed sender and related redirect infrastructure. Cofense reporting identifies the nxcli.io payload paths /fertaq/app/login.php and /fertaq/app/key.php as relevant indicators from this campaign. 1
3
Treat credentials entered on the imitation page as compromised. Change the OpenAI password immediately using a directly opened, trusted OpenAI address. If the account uses API keys, rotate any keys that may have been exposed, review active sessions and recent account changes, and report the incident to the organization’s security team where applicable.
The essential lesson is simple: an urgent ChatGPT billing demand is not proof of a billing problem. Verify account issues from a separately opened official site—not through the link in the email.
Studio Global AI
This page includes a source-backed answer you can continue inside Studio Global.
A Cofense tracked phishing email poses as a ChatGPT billing “final notice,” demands $23.80 within 48 hours, and sends victims to a fake OpenAI login page that captures credentials.
A Cofense tracked phishing email poses as a ChatGPT billing “final notice,” demands $23.80 within 48 hours, and sends victims to a fake OpenAI login page that captures credentials. The payment button routes through notifications.googleapis.com before reaching attacker controlled infrastructure, showing why a familiar service in a link chain is not proof that the destination is safe.
Do not use the email link to resolve billing concerns. Open a browser independently, sign in through auth.openai.com, and reset credentials promptly if you submitted them to the suspected phishing page.