SafePay advisory AA26-293A briefing withdrawn: most of its figures and technical detail are not in the advisory
An audit on 26 October found that this briefing's victim count, dwell time, ransom range, data rates, driver technique and detection rule are not in the CISA advisory, which says at least 600 victims.
By Parminder Kumar Sharma · LinkedIn · · 2 min read
Withdrawn on 26 October 2026
This briefing has been withdrawn. Joint advisory AA26-293A, titled #StopRansomware: SafePay Ransomware, was released on 20 October 2026 and is real. This briefing's account of it was not. Most of its figures and technical claims do not appear in the advisory, and it printed a detection rule that cited CISA as its reference although CISA did not publish it.
What the withdrawn text said, and what the primary pages say. Read on 26 October 2026
| The withdrawn text | What the primary pages say | Page |
|---|---|---|
| 124 victims | The advisory says SafePay has impacted at least 600 separate victims from multiple critical infrastructure sectors. | CISA advisory AA26-293A |
| A 54 percent figure, a 4.8 day dwell time, ransom demands of 500,000 to 12 million dollars and exfiltration at 1.2 TB an hour | None of these appears on the advisory page. The words dwell, BYOVD and RTCore64 do not appear on it either. | CISA advisory AA26-293A |
| A YARA rule and a file footer structure presented as published indicators | No such rule or structure was found in the advisory read. | CISA advisory AA26-293A |
| Release on 22 October | CISA gives the release date as 20 October 2026. | CISA advisory AA26-293A |
Read the advisory itself. This site may rebuild the briefing from it.
This notice replaces the earlier text at the same address, so that links already shared still lead somewhere accurate. On 26 October this site compared its recent briefings with the pages they cite. Where a briefing's specifics could not be tied to a primary page, the briefing was corrected or withdrawn. Nothing that was on the earlier version should be used as a source for the event, and any social post that repeated it should be treated the same way. The corrections page lists each change.
Sources
- Primary#StopRansomware: SafePay Ransomware (AA26-293A)Cybersecurity and Infrastructure Security Agencyaccessed 2026-10-26
- Primary#StopRansomware: SafePay Ransomware (joint advisory PDF, 20 October 2026)FBI Internet Crime Complaint Centeraccessed 2026-10-26


