Cyber & AI intelligence
Briefs indexed3764
Issues37
Published Mondays07:30 CT
█ Ransomware HAPPYFRESH-N0N-RAN 2026-11-16

HappyFresh: N0n Extortion Group Claims Production Database Leak

"The n0n extortion group has listed HappyFresh Group, the online grocery delivery company headquartered in Kuala Lumpur, on its leak site and says it has published data from the company's production order database…"

The n0n extortion group has listed HappyFresh Group, the online grocery delivery company headquartered in Kuala Lumpur, on its leak site and says it has published data from the company's production order database. QPulse, a threat-tracking site, describes the leaked material as including about 131,658 customer email addresses, 90,006 Indonesian mobile numbers, 301,043 order records and 223 internal staff, shopper and driver accounts. HappyFresh has not commented publicly, and no regulator filing or breach notice has appeared. Until the company or a regulator confirms it, treat this as the attacker's claim. The listing is marked "Not Paid: Exposed," which suggests no ransom was paid and the data has been released.

What Happened

QPulse reports that n0n posted the claim on November 16, 2026, and that trackers recorded the listing the same day. The date of the actual intrusion is unknown. The leak post says the data came from the write-ahead log of a production order database. That log records every change made to the database, so it holds live transaction data rather than a backup or a test copy.

QPulse says the order activity in the log runs to late August 2026. If that is accurate, the attackers had the data for about two and a half months before posting it. That fits n0n's process, which SOCRadar describes as three stages: steal data and contact the victim privately, negotiate, then publish if the victim does not pay.

One detail stands out. The company is based in Malaysia, but the phone numbers in the claim are Indonesian. HappyFresh has run its service in Indonesia, so the leaked database may come mainly from that market. If so, Indonesian data protection law could apply alongside Malaysian law.

The HappyFresh listing went up on the same day as another n0n retail victim. QPulse separately reports that n0n listed BoxLunch, a US retailer, on November 16 and claimed to have its shopper search sessions and revenue data. Cyber Daily reports that n0n also claimed a breach of more than one terabyte at Expedia in a November 3 post. Expedia declined to comment on that claim.

What Was Taken

According to QPulse's summary of the leak post, the data includes:

No outlet has independently checked these figures, and the company has not given its own count. The claim does not say that full card numbers or plaintext passwords were taken. The leaked order records show payment status, which does not necessarily mean card details were included.

For defenders, the configuration data and internal accounts matter more than the customer list. Authentication rules and replication roles show how the database accepts connections and which accounts can copy data out of it. The billing records name the employees who own cloud resources, which gives attackers a ready list of phishing targets.

Why It Matters

n0n has grown very quickly. Proven Data, an incident response firm, says the group first posted victims on September 18, 2026. By November 16 it had claimed 221 victims across 42 countries, 129 of them in the previous 30 days. On October 15, SOCRadar counted 93 listed victims, with total ransom demands of $283.7M as of October 19. These counts were taken on different dates, so they do not conflict. Together they show the group's listings more than doubling in about a month. Proven Data puts Retail & E-Commerce at about 9% of n0n's claimed victims, and HappyFresh, BoxLunch and Expedia suggest that share is rising.

Researchers disagree on how n0n operates:

Nothing published about HappyFresh mentions encryption or downtime. So far, this incident looks like data theft and publication only.

Customers whose details are in the leak are likely to receive phishing that refers to real orders, through email and Indonesian mobile numbers. Separately, Nitori, a Japanese furniture retailer, recently disclosed a breach of up to 37.62 million customer records (BleepingComputer). That breach has not been linked to n0n, but it shows how much customer data retailers in Asia are losing this autumn.

The Attack Technique

Nobody has said how n0n got into HappyFresh's systems. The best guide is what is known about the group's other attacks.

SOCRadar says that in September 2026 it found an exposed staging server holding an n0n operator's working files. Those files showed the following methods:

Both firms link that server to at least 23 organisations in 14 countries. OSec notes that although the AI use drew attention, most of the documented break-ins relied on weak or stolen passwords. It adds that reports of n0n exploiting flaws in edge devices such as VPNs and firewalls have not been verified.

The HappyFresh leak includes database configuration and cloud billing data. That points to access deep inside the cloud environment, not just a scrape of a public-facing app. It does not show how the attackers first got in.

What Organizations Should Do

  1. Lock down remote access. Require phishing-resistant multi-factor authentication on every SSL-VPN and firewall management interface. Review login logs from September 2026 onward for high-volume failed logins (credential stuffing) followed by successful ones.
  2. Treat database replication as privileged access. Check client authentication rules (for example, pg_hba.conf on PostgreSQL), limit replication roles to known hosts, and alert on any new replication connection or log-shipping connection.
  3. Rotate credentials if you are exposed. If your staff, contractors or drivers use shared platforms, or you work with HappyFresh, reset passwords and API keys for corporate accounts. Watch for phishing aimed at the employees named in cloud billing records.
  4. Protect your backups. n0n is reported to delete storage buckets in bulk. Turn on object lock or versioning for backups, and keep at least one copy in an account the production credentials cannot reach.
  5. Check whether a claim is real before you respond. If n0n lists your organisation, confirm the claim against your own logs before you deal with the group. Notify regulators within the required deadlines, which apply in both Malaysia and Indonesia.
  6. Point customers to official notices. Tell affected users to rely only on notices the company publishes itself. They should change reused passwords, turn on multi-factor authentication, and treat order-themed messages with suspicion.

Sources: N0n Ransomware Group Exposes Production Database of HappyFresh Grou... | Exclusive: Cyber extortion group claims breach of Expedia, millions... | Japanese furniture giant Nitori says hackers stole 37.6M customer r... | Ransomware Group N0n Claims Data Exfiltration from BoxLunch Storefr... | N0n Ransomware: Data Extortion and Incident Response | Major data breaches: where to find official notices | Dark Web Profile: n0n Ransomware | Weekly situation report: 11/9/26 OSec