Incidents

Arara Message Breach Expands: About 77 Million Email Addresses at Risk

Arara Message breach update: 97 customer-environment servers and about 77 million email addresses at risk. That's addresses, not confirmed individuals.

Arara Message Breach Expands: About 77 Million Email Addresses at Risk

On November 2, PayCloud Holdings published a significant update on the Arara Message breach. The scope now covers 97 servers in customer environments and roughly 77 million email addresses. That figure counts addresses, not confirmed unique individuals.

What has changed in the findings

Earlier descriptions of the incident focused on a single shared environment. The new disclosure changes how far the breach is understood to reach: customer environments are affected as well. According to the published information, up to about 380 companies may be affected, though the findings are still preliminary.

What makes this news is the expanded scale disclosed on November 2. The breach itself should not be described as an event first detected on that date. The service was fully shut down on October 31, and no date has been given for bringing it back online.

A mailing service turned into a fraud tool

The incident also involved attackers using the platform’s infrastructure to send phishing messages. That creates added risk for recipients, who may have trusted mail coming from a familiar service.

For customers, the priority is to determine their own exposure. The total number of addresses doesn’t show what other information was stored in a given environment or which integrations need review. Taking the platform offline does not undo data that was already exfiltrated.

What to do now

  • Check for any direct or indirect use of Arara Message and ASP repica.
  • Ask the vendor to confirm whether your company’s environment is among those affected.
  • Identify the types of data involved, how long the unauthorized access lasted, and how much information was exfiltrated.
  • Review integration keys and administrator accounts, and rotate credentials if they may have been exposed.
  • Set up an alternative channel for delivering critical messages, and warn recipients about attackers impersonating the sender.

SecurHUB’s take

When a vendor expands the scope of an incident, its customers should reassess their own situation. As part of incident response, it makes sense to pair a review of access and integrations with a determination of what data actually left your organization’s environment.

Sources: PayCloud Holdings, INTERNET Watch

AuthorSecurHUB Team

Read more

Related articles

Want to know if this affects your company?

A free consultation with one of our experts — no obligation, in full confidence.

Let's talk