Skip to content

Fraud events ​

Fraud event: an occurrence that is suspected or confirmed to be fraudulent.

Members and their users can submit data related to these fraud events, called contributions, to help identify and prevent future fraudulent activities. By sharing information and collaborating with other participants on the Exchange, contributors can help create a more secure and trustworthy ecosystem that is resistant to fraud and other types of malicious activities.

Types of fraud events ​

Any given fraud event is of one of the following types. The API takes and returns the name in the first column, spelled exactly as shown:

Name in the APIFraud typeDescription
WangiriWangiriThe "missed call scam". Usually detected by a fraud management system, which uploads the details of the event, such as the phone number and the country codes of the parties.
IRSFInternational revenue share fraudFraud that inflates the volume of international traffic to a destination to generate revenue. Usually detected from unusual call patterns.
StolenDeviceStolen deviceAny fraud that involves a stolen device. Usually reported by customers or law enforcement.
IPFraudIP fraudAny fraud that involves a specific IP address. Usually detected by behavioural analysis, geolocation checks and the rate of actions of an address.
SMSA2PSMS A2PFraud that reroutes SMS through SIM boxes and disguises them as legitimate messages. Usually spotted by operators who monitor traffic patterns, contents and sending rates of a phone number.
FlashcallFlash callThe use of missed voice calls to deliver one-time passwords that are otherwise charged as A2P SMS. It bypasses termination charges for A2P SMS.
ScamScamFraud that deceives users through social engineering, such as phishing messages or emails, using phone numbers, email addresses or URLs. Usually identified from unusual transaction patterns and user reports.

Fraud event data model ​

Every fraud event that is submitted and stored on the Exchange adheres to the following model:

DataDescription
Fraud IdentifierThe main identifier of the fraud event.
Could be one of the following:
  1. A range of phone numbers (or a single one) in the E.164 international format: +, then 2 to 16 digits, the first of which is not 0.
  2. A range of IPv4 addresses (or a single one). IPv6 addresses are not accepted.
  3. The IMEI of a device: 15 digits, the last of which is a correct check digit.
  4. An email address.
  5. A URL.
Fraud TypeThe type of the fraud event.
Could be one of the following:
  1. Wangiri
  2. IRSF
  3. StolenDevice
  4. IPFraud
  5. SMSA2P
  6. Flashcall
  7. Scam
Event OriginationThe two-letter code of the country the fraud event originated from (Alpha-2, ISO 3166).
Event DestinationThe two-letter code of the country the fraud event was identified as such (Alpha-2, ISO 3166).
Event ContributorThe peerId of the company that contributed the data.
Event StatusThe status of the event at the time of observing.
Could be one of the following:
  1. Active: the event is stored on the Exchange and has not yet expired.
  2. Expired: the event is stored on the Exchange, but is no longer relevant.
  3. Flagged: the event is stored on the Exchange and is flagged by one of the peers.
Event Expiry DateThe exact time and date until which the event is considered relevant: 60 days after it was submitted, for every fraud type.
Event TimestampThe exact time and date of when the event was submitted.
Event Flag TimestampThe exact time and date of when a contribution has been flagged. Only stored if a contribution has been flagged at the time of observing.
Event FlaggerThe unique ID of the peer that flagged the data. Only stored if a contribution has been flagged at the time of observing.
Privileged StatusThe definition of whether a contribution is privileged.

INFO

For a more technical outlook on what data related to any given fraud event is stored on the Exchange, see Contributions: API data structures.