91APP Got Hacked: 5 Mistakes Your Booking System Should Avoid

91APP Got Hacked: 5 Mistakes Your Booking System Should Avoid

Sarah Chen

by

· 5 min read

Tags:91APPdata securitystaff permissionscustomer communicationOmceanBooking

If a customer reported a suspicious message today, would your studio know who should respond? 91APP's breach investigation began with reports of scam messages. For an owner holding names, phone numbers and booking records, these five failures offer a useful check of your own setup, from unused tools to the first customer warning.

Fictional clay scene: worried executives huddle at a boardroom table on the left while customers on the right raise phones and demand answers.

1. An unpatched tool opened the door

91APP said attackers entered through Appsmith, an internal tool whose software packages had not been updated. The company later removed the tool and acknowledged that its patch management had fallen behind the attacks. 91APP's investigation

Your check: Make one list of the tools connected to your booking business, including old add-ons you rarely open, and put a named update contact beside each. Ask that person or provider how urgent fixes reach you, then remove tools you no longer need instead of leaving them connected indefinitely.

Clay visual metaphor for an unpatched weakness: a burst pipe sprays water across an office while a fictional worker sleeps at the desk.

2. A stolen key unlocked the orders

Once inside, the attackers obtained a database access key from GitLab and used it to reach the order database, according to the investigation reported by iThome. 91APP subsequently changed database access details and rebuilt GitLab permissions. iThome's report

Your check: Review who can access the accounts that connect your booking, payment and customer tools. For each shared or former staff account, decide who still needs access and remove obsolete access; if an outside contractor manages the connection, have them confirm that old access has been revoked and explain who can change it now.

Clay visual metaphor for stolen database access: a hooded figure reaches for an oversized key hanging in the lock of a glowing blue database cylinder.

3. One database put many brands in the same crisis

The compromised database held up to 18 months of transactions, and some records were stolen. Because investigators could not identify the specific orders taken, 91APP used a maximum possible scope covering 1,329 brands and about 4.8 million consumers for notification and claims. That database included names, phone numbers and order records, but no passwords or payment data. CNA's report

Your check: Trace one customer record through your business, from the booking system to downloaded spreadsheets and shared folders. Write down why each copy is still needed, who can open it and when it should be removed; start by clearing unnecessary duplicate exports under your retention policy.

4. Brands heard the warning too late

91APP received the first customer report of scam messages on October 4 and formed an emergency response team on October 8. It later acknowledged that it should have warned brands when that team was formed, rather than waiting to confirm the cause. The company apologised for the delay. 91APP's timeline and acknowledgement

Your check: Rehearse a first-warning message with whoever handles your customer enquiries. Name the person who can approve it, and make the draft say what is known, what customers should do and when the next update will come; give staff a clear contact route for escalating a suspicious call or message.

5. The claims form created another trust hurdle

91APP initially collected compensation applications through Google Forms, prompting concerns about submitting personal information again. On November 6, it moved applications to its official website and apologised for the inconvenience. People who had already applied did not need to resubmit. 91APP's November update

Your check: Walk through your complaint or refund process as a customer who has just received a suspicious message. Start from your known website or app, check that the contact route is easy to find, and remove unnecessary requests for personal information; tell customers how to reach that same route themselves without trusting a forwarded link.

Start with access and communication

OmceanBooking's Roles and Permissions lets you set what staff can view or edit, while built-in messaging supports individual conversations and messages to selected groups. You can review group-message recipients before sending and check notification attempts in Notification History. Start by reviewing one staff role and rehearsing one customer update with your team, before an urgent situation forces the decision.

◆

Was this article helpful?

Try the Booking System for 7 days

All Features Included

7 DAYS FREE$
  • ∞Unlimited bookings
  • ✨All AI features included
  • 🌐Your own branded booking website

No credit card needed

Arrow