Airbnb Ransomware Claim by N0n (Nov 2026)

Low N0n Hospitality United States Unverified

Significant claim

Severity 2.5 Actor 8.6 Data Sens. 3.5 Industry 10.0

Claim Risk Profile

N0n allegedly claims Airbnb breach with consumer data, hashed emails and ad IDs. Unverified leak site post. Read our threat intel analysis and stay alert.

By Yazoul AI · automated

What to do

This claim is unverified. It comes from a post on a leak site or forum, and Yazoul has not confirmed it.

  • If true, files taken from Airbnb may be published, and staff, customers and partners could be targeted with phishing or fraud that uses them.
  • If you deal with Airbnb, wait for its own statement before acting, and treat unexpected messages that mention this incident with suspicion.
  • The group behind the claim: N0n, 26 claims

Leak Site Screenshot

Leak site post claiming Airbnb data breach

Screenshot captured at time of discovery. Image blurred to protect victim PII.

Leak site post claiming Airbnb data breach - full size

Claim Summary

On November 9, 2026, a ransomware group calling itself N0n purportedly listed Airbnb on its dark web leak site. According to the threat actor, the travel and accommodations platform was initially posted anonymously as “Company #173” before being named. The group claims to hold consumer audience data files, including device advertising identifiers and hashed consumer email addresses tied to the company’s customer base. The listing is marked “[NOT PAID - EXPOSED],” suggesting the actor alleges a ransom demand went unmet. No data volume has been disclosed.

None of these claims have been independently verified. At the time of writing, Airbnb has not publicly confirmed or denied the allegation, and no sample data has been validated by third parties.

Threat Actor Profile

N0n is a relatively obscure ransomware operation with no established public track record. Open-source intelligence provides no confirmed victim count, no documented toolset, and no published research references. The group’s known tools and tactics are effectively unknown at this time.

Several factors warrant skepticism. First, the group initially listed the victim anonymously as “Company #173,” a tactic sometimes used by newer or rebranding operations to build visibility before naming targets. Second, the absence of any disclosed data volume or proof-of-leak sample is unusual for established ransomware brands, which typically publish evidence to pressure victims. Third, a group with no verifiable history cannot be assessed for reliability, and the “N0n” branding does not map to any widely tracked ransomware family.

Without corroborating evidence, the group’s credibility should be treated as low to unconfirmed. It is equally possible this is an opportunistic exaggeration, a data-scraping repackage, or a fabricated listing designed to attract attention.

Alleged Data Exposure

The threat actor claims the exposed material consists of consumer audience data files. Specifically, N0n alleges the dataset includes device advertising identifiers and hashed consumer email addresses. Hashed emails, depending on the hashing method used, may be partially reversible through dictionary or rainbow-table attacks, particularly if a weak or unsalted algorithm was applied.

The group has not disclosed the number of records, the date range, or any technical detail about the alleged exfiltration. No samples, screenshots, or file listings have been publicly validated. Yazoul Security has not reviewed any data and does not link to, host, or provide access to leaked material.

Potential Impact

If the claim is accurate, the alleged data types are lower sensitivity than credentials or financial records but still carry privacy and regulatory implications. Advertising identifiers and hashed emails can support cross-site tracking, targeted phishing, or audience re-identification when combined with other datasets. Organizations handling consumer data in the US may face notification obligations depending on state law and the nature of the data. Reputational risk from a public leak site listing can also be significant even when claims are unproven.

What to Watch For

  • Official statement from Airbnb confirming, denying, or downplaying the claim.
  • Publication of verifiable proof-of-leak samples by N0n.
  • Emergence of the N0n brand in other leak site listings, which would help establish a track record.
  • Any independent research or YARA/detection guidance tied to N0n tooling. None is currently available; security teams should rely on generic ransomware detection and monitoring of dark web leak sites.
  • Phishing campaigns referencing the alleged breach, a common follow-on tactic.

Disclaimer

This report is based solely on an unverified claim published on a ransomware group’s leak site. Nothing herein should be treated as fact. Yazoul Security has not independently confirmed the breach, the data types, the data volume, or the involvement of N0n. Ransomware groups routinely exaggerate or fabricate claims to pressure victims. Readers should await official confirmation before drawing conclusions.

Share

Never Miss a Critical Alert

CVE advisories, breach reports, and threat intel — delivered daily to your inbox.