In early November 2026, Synology urged customers to update DSM, its NAS operating system, after ransomware attacks hit devices running outdated versions. According to reporting by The Hacker News on November 3, 2026, Synology said threat actors are exploiting a vulnerability that was already patched in late 2024, with the goal of encrypting data and demanding a ransom.
The malware is called C3RB3R. Customers on Reddit describe files renamed with a ".L0CK3D" extension and a ransom note called "read-me3.txt" dropped in every encrypted folder. Analysts at Qihoo 360 say the ransomware also targets a second set of Synology flaws: two CVSS 9.8 bugs, CVE-2026-13684 and CVE-2026-13639, which Synology fixed in September 2026.
Why should a CIO or IT manager care about a storage appliance? Because network-attached storage (NAS) quietly holds some of the most valuable data in a company: file shares, project archives, finance exports, and very often the backup copies everyone assumes are safe. When the NAS is encrypted, the damage is twice as bad: the primary data and the safety net can disappear in the same incident. Treating NAS devices as part of a broader cybersecurity program rather than as forgotten office hardware is the first lesson of this campaign.
One caution on the facts: Synology did not publicly name the exact flaw being exploited, so the link between specific CVEs and specific attacks should be read as analyst attribution, not as a confirmed root cause.
The core challenge is that the exploited weakness already has a fix, and the victims are the ones who never applied it. Edge and storage devices are the classic blind spot of enterprise patching. They are installed once, they keep working, and nobody is assigned to check them.
Several things make NAS devices especially exposed. They often sit in branch offices and small sites with no dedicated IT staff. They are sometimes published to the internet for remote access or file sharing, which makes them reachable by automated scanners. Their administrator accounts tend to be shared and rarely rotated. And because they are not laptops or servers, they frequently fall outside the endpoint detection tools that would otherwise flag an encryption routine.
The patched versions matter, so here they are as listed in the reporting. For the 2024 advisory, Synology points customers to DSM 7.2.2 build 72806-1 or later, DSM 7.2.1 build 69057-6 or later, DSM 7.2 build 64570-4 or later, DSM 7.1 build 42962-7 or later, and DSM 6.2 build 25556-8 or later. The 2026 fixes arrived in a separate September advisory, so administrators should confirm they are on the latest DSM build and not merely the versions above.
Synology also recommends enabling automatic updates so a device is never left behind. For many sites that single setting would have prevented this incident.
C3RB3R follows the standard ransomware playbook, adapted to a NAS: get code running on the device, encrypt the data, and leave a note. The public reporting does not describe the initial access step in detail beyond saying that attackers exploit flaws in DSM, so the sequence below combines what is documented with how this class of attack generally unfolds.
This is not new ground for NAS ransomware. Families such as QNAPCrypt (eCh0raix) have targeted Synology and QNAP devices since 2019, and Synology itself warned about brute-force attacks leading to ransomware in 2021. What changes in 2026 is the speed at which fresh vulnerabilities are weaponized. Disciplined IT managed services close that gap by making patching, inventory and verification a scheduled routine instead of a good intention.
The goal is not to avoid owning a NAS, it is to make sure a single compromised appliance can never take your business down. A few practical controls deliver most of the protection.
A practical checklist for this week: inventory every Synology and other NAS device, including those in branch offices. Confirm each runs the latest DSM and enable automatic updates. Remove internet exposure and disable default or unused admin accounts. Enable multi-factor authentication where available. Verify that at least one backup copy is offsite and cannot be reached with NAS credentials. Finally, run a restore test and time it.
HIT Communications has more than 30 years of experience connecting and protecting businesses across Latin America, the United States and Europe. For a threat like C3RB3R, we combine the layers that no single device covers.
Our cybersecurity services include a 24/7 security operations center (SOC), SIEM and managed detection and response, so suspicious activity on storage and servers is investigated as it happens. Our IT managed services cover patching, hardening, cloud infrastructure and backup, so updates are applied on schedule and recovery is tested before it is needed. Underneath both, our multi-operator connectivity design delivers segmented, redundant networks that limit how far an incident can spread.
We work with CIOs and IT managers who want one accountable partner rather than five vendors pointing at each other during an incident. If you are not sure how many NAS devices your organization really runs, or who keeps them updated, that is the right place to begin.
The C3RB3R campaign is a reminder that a patch only protects the devices that actually receive it, and that backups stored beside the data they protect are not really backups. The fixes exist, the attacks are happening, and the cheapest moment to act is before a ransom note appears.
Start with an inventory, update DSM, remove internet exposure and make sure at least one backup copy is out of the attacker's reach. If you would like help assessing your exposure or setting up monitored, tested, offsite backups, contact the HIT Communications team and we will review your environment with you.

Find out how we can transform your business. Talk to one of our experts now!
Get in touch