Nightspire ransomware claims Furama Bukit Bintang hotel compromise
Free public brief. The indicators, the detections with Splunk SPL already written (plus Elastic and KQL where they apply), and a Slack alert the next time this touches a vendor you run are in the app — free account, no card.
Nightspire ransomware gang claims breach of Furama Bukit Bintang hotel with 201 compromised user accounts and 14 third-party credentials.
Nightspire ransomware operators have posted a claim of compromise against Furama Bukit Bintang, a hotel chain property. According to the posting on ransomware.live, the attack resulted in 4 compromised employees and 201 compromised user accounts. The attackers also obtained 14 third-party employee credentials and identified 56 points on the victim's external attack surface. DNS records for the victim's domain were also enumerated as part of reconnaissance or post-breach activity.
The claim carries the standard caveats of ransomware gang postings: the actual scope of exfiltration, encryption, or extortion demands cannot be verified from the public posting alone. The article provides no technical indicators, exploitation method, or timeline. Defenders should treat this as confirmation that the victim organization has been targeted, and organizations in the hospitality sector should review access logs, credential compromise, and ransom communications if they share supply chain or service relationships with this victim.
Mentioned in this report
Detection guidance
1 detection for this report is in the app — rules that match its indicators, converted to Splunk SPL, to Elastic where their fields map onto Elastic's integrations and to Microsoft Defender XDR KQL wherever Defender records the activity, plus YARA and Suricata. Three days of it free, no card.
Source reporting: https://www.ransomware.live/id/RnVyYW1hIEJ1a2l0IEJpbnRhbmdAbmlnaHRzcGlyZQ==
What this brief leaves out
This page is the free tier: the write-up, the severity, the names. In the app the same report carries its extracted indicators, its detections (Splunk SPL already written, plus Elastic and Microsoft KQL where they apply), the actors and CVEs it names as live profiles, and the vendor research on the same campaign — the primary source the news paraphrased, cited and read directly.
It sits in a corpus of 13,854 reports from 146 sources, 616 of them written in the last seven days, and it grows through the day.
A new account starts with three days of all of it, no card, then keeps the government and CERT reporting free. Name the vendors you run and Slack hears about the reports that touch them — about forty a week that are yours, not the four hundred that are not.
Create a free account What it costs