A password in Wyndham's Android app exposed customer data, TechCrunch reported
Wyndham has acknowledged a cybersecurity incident after a security researcher found a password inside the company's Android app that granted access to an internal customer database, TechCrunch reported on November 9, 2026. According to that report, the database was hosted by Salesforce and included customer names, email addresses, Wyndham member numbers, login tokens and company files. The credential was revoked soon after TechCrunch contacted the company, and Wyndham said it had no evidence of unauthorized access. This article summarizes that reporting and a November 10 TechRadar follow-up. It is not an independent examination of Wyndham's app or database.
Real, reported: based on the public sources cited below. Nothing added or dramatized. Sources checked November 11, 2026, at 7:15 AM ET (EST). The description of what was exposed comes from the researcher as reported by TechCrunch. The finding that there is no evidence of unauthorized access is Wyndham's statement, not a finding we independently verified.
What the researcher told TechCrunch
Security researcher Robert Wiggins of What Security "exclusively told TechCrunch that he found a password inside the source code of Wyndham's Android app, which granted access to an internal company database, hosted by tech company Salesforce." Wiggins told the publication that the credential exposed personal information including customer names, email addresses and Wyndham member numbers. TechCrunch reported that the database also stored customer login tokens, called JWTs, that keep customers logged in to their apps without repeatedly entering passwords, and that it also contained Wyndham files and documents.
According to Wiggins, the database had millions of entries, but he was unable to determine an accurate number of exposed customer records. TechCrunch noted that Wyndham touts some 129 million enrolled rewards members. That membership figure is not the same as a confirmed count of exposed records. We do not treat it as one.
Wiggins told TechCrunch he could not find a way to report the flaw to Wyndham and asked the publication for help. TechCrunch reported that soon after it contacted Wyndham's cybersecurity staff, the exposed credential was revoked, "preventing any further access to the database."
What Wyndham has said, and what it would not say
"Our team has taken steps to address the issue," a Wyndham spokesperson told TechCrunch. "Our security teams have no evidence of any unauthorized access," the statement added, without further details about that claim. TechCrunch reported that the spokesperson would not say whether the company had the technical means, such as server logs, to determine if anyone had accessed the customer database before Wiggins's discovery. The company also would not say how long the password had been embedded in the app, how it planned to ship a long-term fix, whether it planned to notify customers, or whether it planned to disclose the incident to U.S. regulators, including a possible notice to the U.S. Securities and Exchange Commission for a material cybersecurity incident.
TechRadar, in a November 10, 2026 article, also reported the incident, citing TechCrunch's interview and repeating the same spokesperson statements. TechRadar wrote that tokens of this kind, if still active, could allow someone to reach a user's app session without knowing that user's password, and that personal information and company documents could be used in phishing. Those are TechRadar's explanations of the risk, not a confirmed account of how the data was used. TechRadar likewise reported that the number of people affected and any prior access remain unclear.
A company statement that there is no evidence of unauthorized access is only as strong as the logs and review behind it. Because Wyndham would not say whether it had those logs, that statement should not be read as proof that nobody else reached the database.
What this does not establish
TechCrunch reported that this was Wiggins's second public discovery of hardcoded credentials in two weeks, after a separate finding in Applebee's app. That is a statement about two distinct disclosures. We do not treat the Applebee's report as evidence of what happened at Wyndham, and we do not invent a combined victim count.
TechCrunch also explained, in general terms, why developers usually avoid leaving passwords in shipped apps: anyone with a copy of the software can extract the password and use it to reach the associated server or database. The publication reported that many cases of hardcoded credentials are automatically scored with a maximum vulnerability severity rating. That is TechCrunch's general description of the issue class, not a formal severity score assigned in a Wyndham advisory cited here.
When asked about Wyndham's response, Wiggins told TechCrunch that he was glad the company fixed the issue, but noted that without visibility into any past activity, someone with malicious intent could have leaked large amounts of customers' personal information, the publication reported. TechCrunch reported that the company would not say whether it planned to set up a vulnerability disclosure program so that outside researchers could report flaws privately.
No official Wyndham customer notice was among the sources cited in this article. The absence of a public customer letter in those articles does not prove that no notice will be issued later, and it does not tell any individual member whether their record was in the database.
Our advice (general guidance)
If you use the Wyndham app or belong to a Wyndham rewards program, treat unexpected messages about a "data breach," "account lock" or "rewards verification" with caution. Compare any notice with information on Wyndham's own website rather than following a link in email or text. A message that asks for a password, a one-time code or payment details is a warning sign.
Because login tokens were among the data the researcher described, consider signing out of the official app and signing back in through the company's own app or website, and review recent account activity for reservations or profile changes you did not make. If you reuse the same password on other sites, change those passwords as well, and use a unique password for your hotel account. Watch for phishing that uses your name, email address or member number.
Wyndham has said it has no evidence of unauthorized access, but it has not, in the cited reporting, confirmed whether every record was reviewed or whether customers will be notified. If you later receive an official notice, keep a copy and follow the instructions on the company's own site. For U.S. readers, the Federal Trade Commission points people to IdentityTheft.gov for recovery steps and related credit-freeze education.
These are editorial precautions, not individualized legal, travel or security advice.
Featured in FraudMeNot Daily, Nov 11, 2026.
Sources
- TechCrunch: Hotel giant Wyndham exposed customer data after app security lapse (Nov 9, 2026, 3:03 PM PST)
- TechRadar: Wyndham confirms it exposed hotel customer data after expert finds flaw in app security (Nov 10, 2026)
- FTC IdentityTheft.gov (U.S. recovery resource)
Published November 11, 2026 by FraudMeNot Team. Label: Real, reported.