2RedBeans, a dating platform run by Embrace Inc. whose users are mainly Chinese speakers, says an unauthorized party got into one of its internal systems on November 4, 2026 and copied member information until the company detected and stopped the access on November 5. The company posted the same notice in English and Chinese on November 18. Both versions say about 1.3 million member accounts are affected. No other figure has been published. No security outlet has reported the incident independently, no regulator filing has been made public, and no group has claimed responsibility.
What Happened
The company says it closed the access, fixed the underlying issue and removed the accounts the intruder had used, all on the day it detected the activity. It then reviewed what had been accessed before notifying members, 13 days after detection. 2RedBeans has reported the incident to the FBI's Internet Crime Complaint Center (IC3) and to the hosting provider whose network the attacker used. It says law enforcement did not ask it to delay the notice.
The company also says it is "continuing to review our records, including earlier activity." That leaves open whether the access began before November 4. The FAQ in the Chinese notice tells anyone who registered before November 5, 2026 to assume their information may be affected.
What Was Taken
According to the notice, the data that may have been copied for about 1.3 million accounts includes:
- Name, gender, age, date of birth, city, state or province, country, and answers to profile questions
- Profile photos, including photos that had not yet been approved for display
- Email addresses, and phone numbers where members had verified one
- IP addresses used to sign up and log in, with approximate locations
- Reports and feedback submitted by or about members, including attached screenshots
- Account status, such as whether an account is active or under review
The company says passwords, payment card and PayPal details, government ID numbers and linked social media accounts were not affected, and that its messaging system was not accessed. There is one important exception: screenshots of private conversations that members attached to abuse reports are included in the exposed report data.
Why It Matters
This leak is more sensitive than the contact-detail breaches reported elsewhere this autumn. Save-On-Foods (CBC News), SOGO in Hong Kong (The Standard, about 820,000 members, also detected on November 5) and Applebee's (TechCrunch) mostly exposed names, emails, phone numbers and dates of birth. In 2RedBeans' case, the data combines identity, location, photos and the content of members' reports about each other.
The company's own guidance says the biggest risk is romance and investment fraud, not account takeover. Scammers can use real photos to build convincing fake profiles and use personal details to win trust. The Chinese notice specifically warns about requests to move conversations to WhatsApp, WeChat or Telegram, and about "guaranteed" crypto investments. Unapproved photos and moderation reports may contain material members never meant anyone to see. Semrush ranks 2redbeans.com around 199,000th globally by traffic, so this is a niche platform, but its user base is closely knit and that makes targeted scams easier.
The Attack Technique
2RedBeans has not said how the intruder got in. Its account of the fix gives some clues. The company says it "removed the accounts that had been used", blocked the attacker's network, and has since limited internal staff tools so they can only be used from approved staff networks. Read together, these suggest that an internal or admin tool could be reached from the internet and was accessed with accounts the attacker controlled or had compromised, from rented hosting infrastructure. The company has not confirmed this.
Other recent incidents involved the same kind of exposed internal access. TechCrunch reported that Applebee's left a database password inside its Android app. Kaspersky's Securelist recently described how weak isolation in a cloud provider's internal management services led to a wider compromise. There is no evidence that either technique was used against 2RedBeans.
What Organizations Should Do
- Take internal and moderation tools off the public internet. Put them behind a VPN or zero-trust access with device checks. Do not rely on a login page alone.
- Audit staff and service accounts regularly. Remove stale accounts, require phishing-resistant MFA, and alert when an account is created or logs in from a new place, especially from hosting provider IP ranges.
- Watch for bulk data copying. Rate-limit and alert when admin tools export or browse records at a scale no human moderator would.
- Treat moderation data as sensitive. Abuse reports, screenshots and unapproved uploads need tighter access controls and shorter retention than ordinary profile data.
- Look back further than the detection date. Like 2RedBeans, check logs from before the first known intrusion to establish when access actually started.
- Know your notification deadlines in advance. Deadlines vary by country. Under the Philippine privacy regulator's rules, for example, both the regulator and affected people must be told within 72 hours. Have a disclosure plan ready before you need it.
Sources: Notice of Data Breach | How your cloud could get hacked: an analysis of a real-world vulner... | Save-On-Foods loyalty program members had personal information acce... | Applebee's exposed customers' personal data after leaving database... | 2redbeans.com Website Traffic, Ranking, Analytics September 2026 | 数据泄露事件通知 | SOGO and Chow Sang Sang report data breaches affecting up to 820,00... | Data breach notification to the NPC: Advisory 2026-02 LWPS