How the attack works
PingOne sends its codes to users as notifications: the one-time passcode of an MFA step by email, SMS, voice or WhatsApp, the recovery code of a forgotten password by email, verification codes for new accounts, and the notice that a new device was paired. By default they go out through Ping's own email service and telephony provider. An environment can replace both. The email delivery settings hold either the organization's own SMTP server (host, port, user name and password) or an external email service that PingOne calls over HTTP. The phone delivery settings hold accounts at Twilio or Syniverse, or a custom provider, for which Ping documents a request URL that receives the recipient's number and the message text. WhatsApp has its own delivery settings, and the notifications settings decide in which order the configured providers are used and which sender address appears on email.
Whoever runs the server at the other end of these settings sees every message. An attacker who can edit them does not need to phish anyone: they start a password recovery for an account and read the recovery code, or sign on with a known password and read the passcode. PingOne records the changes as EMAIL_DELIVERY_SETTINGS, PHONE_DELIVERY_SETTINGS, INSTANT_MESSAGING_DELIVERY_SETTINGS and NOTIFICATIONS_SETTINGS audit activities. Changes to the push credentials of a mobile application (PUSH_CREDENTIALS) are a different case: push messages carry no code, but without valid credentials PingOne cannot send them, and users fall back to weaker methods. The attack described here follows from what Ping documents about these settings: no public incident report describes it for PingOne.
Log source: the rules read PingOne audit activities. Include these event types in the PingOne webhook that feeds the SIEM, or poll the Audit Activities API, for every environment.
What an attacker needs
- A PingOne role that can edit the notification configuration of the environment. Ping names the Environment Admin role for phone delivery settings, notifications settings and SMTP settings.
- A mail server, messaging account or HTTP endpoint under the attacker's control to receive the messages.
Impact
Every one-time passcode and recovery code that PingOne sends through the changed provider is readable by the attacker, for every user of the environment. Accounts that can recover a password by email, or that use email, SMS or voice as their second factor, can be taken over one after another, and the users notice at most a delayed or missing message.
Detection rules
PingOne Email Delivery Settings Updated or Deleted
Detects a change to how a PingOne environment sends email (audit activities EMAIL_DELIVERY_SETTINGS.UPDATED and EMAIL_DELIVERY_SETTINGS.DELETED, described by Ping as Email Delivery Settings Updated and Deleted). Ping documents that an environment has a single set of email delivery settings, which holds either the organization's own SMTP server (host, port, user name, password) or an external email service that PingOne calls over HTTP. Password recovery codes, email passcodes and verification codes leave through that server, so whoever runs it can read them. The activity does not say which host or service was set: read the settings and compare them with your reviewed copy. A deletion removes the custom server or service. It is matched so that a change that is made and removed again is seen from both ends.
title: PingOne Email Delivery Settings Updated or Deleted
id: 33aa5cd6-9f51-4be8-ba65-0514ac30b8aa
status: experimental
description: >-
Detects a change to how a PingOne environment sends email (audit activities
EMAIL_DELIVERY_SETTINGS.UPDATED and EMAIL_DELIVERY_SETTINGS.DELETED,
described by Ping as Email Delivery Settings Updated and Deleted). Ping
documents that an environment has a single set of email delivery settings,
which holds either the organization's own SMTP server (host, port, user
name, password) or an external email service that PingOne calls over HTTP.
Password recovery codes, email passcodes and verification codes leave
through that server, so whoever runs it can read them. The activity does not
say which host or service was set: read the settings and compare them with
your reviewed copy. A deletion removes the custom server or service. It is
matched so that a change that is made and removed again is seen from both
ends.
references:
- https://attack.mitre.org/techniques/T1111/
- https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
- https://developer.pingidentity.com/pingone-api/platform/notifications/email-delivery-settings/index.html
- https://developer.pingidentity.com/pingone-api/platform/notifications/notifications-settings-smtp/index.html
author: Forestall
date: 2026-11-18
tags:
- attack.credential-access
- attack.t1111
logsource:
product: pingone
service: audit
detection:
selection:
action.type:
- EMAIL_DELIVERY_SETTINGS.UPDATED
- EMAIL_DELIVERY_SETTINGS.DELETED
condition: selection
falsepositives:
- A planned move to the organization's own mail server or to another email service, and the renewal of the password or token stored in the settings. These changes are rare, so confirm each one with the change record.
level: medium
False positives
- A planned move to the organization's own mail server or to another email service, and the renewal of the password or token stored in the settings. These changes are rare, so confirm each one with the change record.
PingOne Notifications Settings Updated
Detects a change to the notifications settings of a PingOne environment (audit activity NOTIFICATIONS_SETTINGS.UPDATED, described by Ping as Notification Settings Updated). Ping documents what the settings hold: the fallback chain of SMS and voice providers, which is the order in which the configured phone delivery accounts are tried, the email provider fallback chain, which switches between a custom mail server or provider and Ping's own, and the sender and reply-to names and addresses of email. Moving a provider to the front of a chain decides who receives the one-time passcodes and recovery codes of the environment, and a changed reply-to address decides who receives the answers of users. The activity does not say which setting changed: read the settings and compare them with your reviewed copy.
title: PingOne Notifications Settings Updated
id: 4a1732a0-b5e3-48fa-9f59-c0d4d59bd3fb
status: experimental
description: >-
Detects a change to the notifications settings of a PingOne environment
(audit activity NOTIFICATIONS_SETTINGS.UPDATED, described by Ping as
Notification Settings Updated). Ping documents what the settings hold: the
fallback chain of SMS and voice providers, which is the order in which the
configured phone delivery accounts are tried, the email provider fallback
chain, which switches between a custom mail server or provider and Ping's
own, and the sender and reply-to names and addresses of email. Moving a
provider to the front of a chain decides who receives the one-time
passcodes and recovery codes of the environment, and a changed reply-to
address decides who receives the answers of users. The activity does not
say which setting changed: read the settings and compare them with your
reviewed copy.
references:
- https://attack.mitre.org/techniques/T1111/
- https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
- https://developer.pingidentity.com/pingone-api/platform/notifications/notifications-settings/index.html
author: Forestall
date: 2026-11-18
tags:
- attack.credential-access
- attack.t1111
logsource:
product: pingone
service: audit
detection:
selection:
action.type: NOTIFICATIONS_SETTINGS.UPDATED
condition: selection
falsepositives:
- Changes to the sender name or the default language of notifications, and a planned switch of provider order after a new provider was set up. Confirm with the change record.
level: medium
False positives
- Changes to the sender name or the default language of notifications, and a planned switch of provider order after a new provider was set up. Confirm with the change record.
PingOne Phone or Instant Messaging Delivery Settings Changed
Detects a change to the accounts a PingOne environment uses to send SMS, voice and WhatsApp messages (audit activities PHONE_DELIVERY_SETTINGS and INSTANT_MESSAGING_DELIVERY_SETTINGS, created, updated or deleted). Ping documents phone delivery settings as the accounts that can be used for sending an SMS or voice message, up to 10 per environment: accounts at Twilio or Syniverse, or a custom provider with a request URL that receives the recipient's number and the message. The instant messaging settings hold the WhatsApp application used for notifications. One-time passcodes leave through these accounts. A new or changed provider is in use once the fallback chain of the notifications settings puts it first, which a separate rule of this page reports. The activity does not say which account or URL was set: read the settings and compare them with your reviewed copy.
title: PingOne Phone or Instant Messaging Delivery Settings Changed
id: befae89d-3036-4e39-8444-90744ebcec2b
status: experimental
description: >-
Detects a change to the accounts a PingOne environment uses to send SMS,
voice and WhatsApp messages (audit activities PHONE_DELIVERY_SETTINGS and
INSTANT_MESSAGING_DELIVERY_SETTINGS, created, updated or deleted). Ping
documents phone delivery settings as the accounts that can be used for
sending an SMS or voice message, up to 10 per environment: accounts at
Twilio or Syniverse, or a custom provider with a request URL that receives
the recipient's number and the message. The instant messaging settings hold
the WhatsApp application used for notifications. One-time passcodes leave
through these accounts. A new or changed provider is in use once the
fallback chain of the notifications settings puts it first, which a
separate rule of this page reports. The activity does not say which account
or URL was set: read the settings and compare them with your reviewed copy.
references:
- https://attack.mitre.org/techniques/T1111/
- https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
- https://developer.pingidentity.com/pingone-api/platform/notifications/phone-delivery-settings/index.html
- https://developer.pingidentity.com/pingone-api/platform/notifications/instant-messaging-delivery-settings/index.html
author: Forestall
date: 2026-11-18
tags:
- attack.credential-access
- attack.t1111
logsource:
product: pingone
service: audit
detection:
selection:
action.type:
- PHONE_DELIVERY_SETTINGS.CREATED
- PHONE_DELIVERY_SETTINGS.UPDATED
- PHONE_DELIVERY_SETTINGS.DELETED
- INSTANT_MESSAGING_DELIVERY_SETTINGS.CREATED
- INSTANT_MESSAGING_DELIVERY_SETTINGS.UPDATED
- INSTANT_MESSAGING_DELIVERY_SETTINGS.DELETED
condition: selection
falsepositives:
- A new contract with an SMS or voice provider, a new sender number, or the first setup of WhatsApp notifications. These changes are rare, so confirm each one with the change record and with the team that owns the provider account.
level: medium
False positives
- A new contract with an SMS or voice provider, a new sender number, or the first setup of WhatsApp notifications. These changes are rare, so confirm each one with the change record and with the team that owns the provider account.
PingOne Application Push Credentials Created, Updated or Deleted
Detects a change to the push credentials of a native application in PingOne (audit activities PUSH_CREDENTIALS.CREATED, PUSH_CREDENTIALS.UPDATED and PUSH_CREDENTIALS.DELETED). Ping documents push credentials as required for sending push notifications to a native application, in three types: APNS for Apple, FCM_HTTP_V1 for Google and HMS for Huawei. A push message carries no passcode, so this change does not disclose a factor the way a changed email or SMS provider does. Its effect is on availability: with wrong or deleted credentials PingOne cannot send the push, and users whose policy allows another method fall back to it, often a passcode by SMS or email. The rule is for review, as context for the other rules of this page.
title: PingOne Application Push Credentials Created, Updated or Deleted
id: 8a0ecc16-4a67-4ca9-b22c-9db4f38f29e8
status: experimental
description: >-
Detects a change to the push credentials of a native application in PingOne
(audit activities PUSH_CREDENTIALS.CREATED, PUSH_CREDENTIALS.UPDATED and
PUSH_CREDENTIALS.DELETED). Ping documents push credentials as required for
sending push notifications to a native application, in three types: APNS
for Apple, FCM_HTTP_V1 for Google and HMS for Huawei. A push message carries
no passcode, so this change does not disclose a factor the way a changed
email or SMS provider does. Its effect is on availability: with wrong or
deleted credentials PingOne cannot send the push, and users whose policy
allows another method fall back to it, often a passcode by SMS or email.
The rule is for review, as context for the other rules of this page.
references:
- https://attack.mitre.org/techniques/T1111/
- https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html
- https://developer.pingidentity.com/pingone-api/platform/applications/application-mfa-push-credentials/index.html
author: Forestall
date: 2026-11-18
tags:
- attack.credential-access
- attack.t1111
logsource:
product: pingone
service: audit
detection:
selection:
action.type:
- PUSH_CREDENTIALS.CREATED
- PUSH_CREDENTIALS.UPDATED
- PUSH_CREDENTIALS.DELETED
condition: selection
falsepositives:
- The renewal of an Apple push certificate or key, a new Firebase service account, and the setup of a new mobile application. Confirm with the team that owns the application.
level: low
False positives
- The renewal of an Apple push certificate or key, a new Firebase service account, and the setup of a new mobile application. Confirm with the team that owns the application.
Detection logic
Patterns that need more than one event, a baseline or knowledge of your own environment. Each is a hypothesis to build and tune in your SIEM, not a ready rule.
Delivery settings changed and a password recovery for a privileged user soon after
The change pays off when a code is sent through the new provider. A change to email delivery or to the notifications settings that is followed by a password recovery for an administrator, or by recoveries for several users in a row, is the diverted channel being used to take accounts over.
- Note each
EMAIL_DELIVERY_SETTINGS.UPDATED,PHONE_DELIVERY_SETTINGS.CREATED,PHONE_DELIVERY_SETTINGS.UPDATEDorNOTIFICATIONS_SETTINGS.UPDATEDactivity with its actor and time. - Look for
PASSWORD.RECOVERYactivities in the same environment within the next 24 hours, and read the user each one concerns fromresources.namewhereresources.typeis USER. - Compare those users with your list of administrators and other privileged accounts, and count how many different users recovered a password in the period.
- Compare
source.ipAddressof the recoveries with the address of the settings change.
EventsEMAIL_DELIVERY_SETTINGS.UPDATEDPHONE_DELIVERY_SETTINGS.CREATEDPHONE_DELIVERY_SETTINGS.UPDATEDNOTIFICATIONS_SETTINGS.UPDATEDPASSWORD.RECOVERY
LimitsUsers recover passwords every day, so the join needs your own list of privileged accounts to mean something. Ping's event list does not describe at which step of a recovery the activity is written. An attacker who only reads passcodes of accounts whose password they already know starts no recovery at all.
Triage
- Identify the actor (actors.user.name or actors.client.name) and check for an approved change, such as a planned move to the organization's own mail server or a new SMS contract.
- Read the current settings through the API or the console. For email, check the SMTP host or the request URL of the external service. For SMS and voice, check the provider type, the account and for a custom provider the request URL. For the notifications settings, check the provider order and the sender and reply-to addresses.
- Compare each value with the reviewed copy. A host, URL or account that does not belong to the organization or its known suppliers is the change to act on.
- List the password recoveries (
PASSWORD.RECOVERY) and the sign-ons that used an email, SMS or voice passcode since the change, starting with administrators. - Review what else the actor changed in the same session, such as MFA policies, administrator security and role assignments.
Response
Once the attack is confirmed:
- Restore the delivery settings and the provider order from the reviewed copy, or reset them so that PingOne's own services are used again, and confirm with a test message where it is delivered.
- Treat every passcode and recovery code sent since the change as disclosed. End the sessions of users who signed on with an email, SMS or voice passcode in that period and reset the passwords that were recovered.
- Suspend the administrator or worker application that made the change, remove the role that allows it, and for a worker application replace its client secret.
- Change the credentials stored in the settings, such as the SMTP password and the provider account secrets, because the actor could use the accounts they belong to.
- Review MFA devices and passwords of administrators that changed since the first unexplained change, and remove what their owners do not recognize.
Mitigation
- Limit the Environment Admin role and custom roles that can edit notification configuration, and require a change record for every edit.
- Keep a reviewed copy of the email delivery settings, phone delivery settings, WhatsApp settings and notifications settings of every environment, and compare it after every change event.
- Use FIDO2 or an authenticator app as the MFA method for administrators and other privileged users, because those factors do not pass through a delivery provider.
- Do not allow account recovery by email for administrators, so that a diverted recovery code cannot open an administrator account.
- Alert on these event types in every environment, including test environments that share users with production.
Frequently asked questions
Which messages pass through the delivery provider of a PingOne environment?
Ping's notification templates list them. The strong authentication template sends a push notification or a one-time passcode through email, SMS or voice. The recovery code template sends the email with the code a user needs to reset a forgotten password. Other templates carry verification codes for new accounts and the notice that a new device was paired. All of them leave through the provider configured for that channel.
Why is a custom SMS provider a risk when it is changed?
For a custom provider Ping documents a request URL, the provider's remote gateway or customer gateway URL, to which PingOne sends the recipient's number and the message. The message is the text with the passcode. An administrator who replaces the URL, or adds a new provider and moves it to the front of the fallback chain in the notifications settings, decides who receives that text.
Does the audit activity show which server or account was set?
Ping's event list gives these activities only the common attributes, such as the actor, the source address and the resource, and no attribute for the new host, URL or account. The rules therefore report that the settings changed, not what they changed to. Read the settings after every alert and compare them with your reviewed copy.
Has this been seen in attacks on PingOne tenants?
No public incident report describes it for PingOne. The page follows from Ping's documentation: the environment can route email, SMS, voice and WhatsApp notifications through a server or account of the customer's choice, and those notifications carry passcodes and recovery codes.
References
- MITRE ATT&CK T1111: Multi-Factor Authentication Interception
- PingOne Platform API: Email delivery settings
- PingOne Platform API: Notifications settings (SMTP)
- PingOne Platform API: Phone delivery settings
- PingOne Platform API: Instant messaging delivery settings
- PingOne Platform API: Notifications settings
- PingOne Platform API: Notifications templates
- PingOne Platform API: Application MFA push credentials
- PingOne Platform API: Audit reporting events