If your files and your backups both live on a Synology NAS, ransomware is now going after that box. The security firm 360 says a Cerber variant called C3RB3R has been encrypting Synology devices since early October, using two flaws Synology fixed on September 18.
Get the CyberExperts Daily Brief: the day's top security news in 5 minutes. Free.
The attack is the old kind. Nobody needs to click anything. A NAS that missed the September DSM update and is reachable from the internet is the target.
A NAS that holds your files and your backups is one box to encrypt. The fix has been out since September 18.
The 5-Minute Cyber BriefDon’t Miss the Policy Changes That Affect Security Decisions
Get the key CISA actions, new regulations, guidance, and risk shifts in a quick daily brief.
By subscribing you agree to our Privacy Policy.
Free. Weekday mornings. 5 minutes or less.
Ransomware is locking Synology NAS boxes that skipped the September update
On October 29, 360’s anti-ransomware team reported repeated attacks on Synology NAS devices by C3RB3R, a variant of the Cerber ransomware family. Files get the extension .L0CK3D, and each folder gets a ransom note named read-me3.txt. 360 says the entry point is two remote, unauthenticated flaws in DiskStation Manager, CVE-2026-13639 and CVE-2026-13684, both rated 9.8.
Synology fixed both in advisory Synology-SA-26:13 on September 18, along with six other DSM flaws. The advisory lists no mitigation, so the update is the fix.
One caution from a secondary report: TrebSec says an incident response team has seen a victim already on a recent DSM 7.4.1 build and cannot rule out another entry route, such as a package, container or stolen credentials. Treat the DSM update as necessary, and the checks below as the rest of the job.
Home offices and small teams that keep files and backups on one NAS
The exposed group is every Synology unit on DSM 7.4 before 7.4-90075, 7.3 before 7.3.2-86009-4, 7.2.2 before 7.2.2-72806-9 or 7.2.1 before 7.2.1-69057-12. That includes the forgotten boxes at branch offices, in labs and in home offices.
The damage is worst for people who treat the NAS as the backup. Ransomware that can write to a shared folder can also hit backup copies stored where the NAS has write access. TrebSec says no free public decryption tool has been confirmed, so recovery depends on a copy the attackers could not reach.
Update DSM, keep it off the internet, and make one copy the NAS cannot touch
- Open Control Panel, then Update and Restore, and install DSM 7.4-90075, 7.3.2-86009-4, 7.2.2-72806-9, 7.2.1-69057-12 or later for your branch. Turn on automatic DSM updates.
- Remove router port forwards to the NAS management ports. For remote access, use a VPN or the vendor’s relay service, and turn on the firewall with a trusted-address list.
- Turn on two-step verification and automatic IP blocking, and disable the default admin account.
- Turn on snapshots for shared folders with tamper protection, and keep one backup on a drive that is disconnected from the NAS and the network between runs.
Forward this
For whoever looks after our file server or the NAS in the back office: ransomware is encrypting Synology NAS devices that missed the update Synology released on September 18, and it hits the backups stored on the same box. Can we check the DSM version on every Synology we own, update it today, make sure its admin page is not reachable from the internet, and confirm one backup copy lives somewhere the NAS cannot write to?
Details
- CVEs: CVE-2026-13639 (insufficient entropy in login logic, CWE-331) and CVE-2026-13684 (improper output encoding in SCGI, CWE-116). Both CVSS 9.8 per Synology, network, no privileges, no user interaction. Synology-SA-26:13 also covers CVE-2026-13635, CVE-2026-13673, CVE-2026-6205, CVE-2026-13666, CVE-2026-13623 and CVE-2026-13683.
- Fixed DSM releases: 7.4-90075, 7.3.2-86009-4, 7.2.2-72806-9 and 7.2.1-69057-12, published September 18, 2026. Mitigation listed by Synology: none.
- Ransomware traits (360): ChaCha8 file encryption with a per-file key wrapped in RSA-2048, encrypted files renamed
.L0CK3D, 27 system directories skipped, ransom noteread-me3.txt.
Hunt / verify
- Search the NAS for files ending in
.L0CK3Dand forread-me3.txtin shared folders. - Read Log Center for logins from unexpected addresses and for bursts of file changes, and review shared links, packages and containers you no longer use.
- If a device is already hit, disconnect it from the network, keep the ransom note, logs and sample files, and do not reboot or reinstall until you have judged the recovery options. TrebSec points reports to the FBI’s IC3.
Source: Synology advisory SA-26:13; 360 report on C3RB3R (Chinese)
Sources
- Synology: Synology-SA-26:13 DSM
- 360: Cerber ransomware attacks on Synology NAS, early warning (Chinese)
- pwn.watch: C3RB3R (Cerber) ransomware hits Synology NAS devices
- TrebSec Brief: C3RB3R Ransomware Is Encrypting Synology NAS Devices That Missed a September Patch
- NVD: CVE-2026-13639
Start your morning with the signal that matters.
Get the biggest cybersecurity developments, why they matter, and where to go deeper on CyberExperts.
By subscribing you agree to our Privacy Policy.
Free. Weekdays. Built for operators.