ProBackend
Threats & Attacks
3 days ago5 min read

Synology urges DSM upgrades amid C3RB3R attacks on vulnerable storage devices

Synology urges DSM upgrades amid C3RB3R attacks on vulnerable storage devices

Synology urges customers to update DSM and restrict internet access to NAS management interfaces amid C3RB3R ransomware attacks. Learn what is known and how administrators can reduce exposure.

Synology urges DSM upgrades amid C3RB3R attacks on vulnerable storage devices

A network storage appliance can hold the files an organization depends on every day. That makes Synology’s latest warning worth acting on now: the company says customers should update DiskStation Manager (DSM) immediately amid ongoing C3RB3R ransomware attacks targeting NAS devices. It also recommends enabling automatic updates. If a device’s management interface is reachable from the internet, take that exposure seriously and remove it while bringing the system up to date. (BleepingComputer’s report)

The warning does not identify the vulnerability used in the current attacks. Synology instead pointed to a November 2024 security advisory covering several flaws and their fixes. That distinction matters. The advisory is useful for checking software versions, but it does not establish which flaw the attackers are exploiting today. Administrators should avoid treating a plausible connection as a confirmed attack method. (BleepingComputer’s report)

BleepingComputer reported the warning and the available remediation details on November 2, 2026, with a later update noting Synology’s response. (Read the report)

What the warning says—and what it doesn’t

Synology urged customers to update DSM immediately and recommended automatic updates to keep systems current. When asked which flaw was being exploited in the C3RB3R attacks, the company referred the publication to the 2024 advisory rather than naming a specific vulnerability. The advisory described vulnerabilities that could allow arbitrary code execution, file reading, or file writing on unpatched devices. (BleepingComputer’s report)

Those are serious capabilities, but the available reporting does not confirm that any one of the listed flaws is the entry point in the ongoing campaign. This is a small but important point in incident response: patch against the vendor’s stated fixed versions, while keeping the unknown exploitation detail explicitly unknown. Guesswork can distract teams from the practical controls they can apply immediately.

The November 2024 advisory’s reported fixed releases differ by DSM branch: DSM 7.2.2-72806-1 or later, DSM 7.2.1-69057-6 or later, DSM 7.2-64570-4 or later, DSM 7.1.1-42962-7 or later, and DSM 6.2.4-25556-8 or later. BleepingComputer characterizes the DSM 7.x entries as critical severity and DSM 6.2 as moderate. Check the report’s account of Synology’s advisory and the advisory itself for the applicable branch and update details; don’t assume that a version number from another branch is interchangeable.

Immediate steps for NAS administrators

Start with inventory. Identify each Synology appliance, its DSM branch and installed release, and whether its management web interface is accessible from outside the organization. An incomplete asset list makes even a clear vendor warning hard to act on. Check remote sites and devices maintained by third parties, too, if they fall within your responsibility.

Next, install the appropriate fixed release listed in the advisory and verify that the upgrade completed. Synology recommends enabling automatic updates, which can reduce the time a device remains behind when future updates are available. Automatic updating is not a substitute for confirming that this particular fleet is protected; administrators should still verify the resulting versions. (BleepingComputer’s report)

Restrict internet access to the management interface. The report specifically advises NAS owners to block internet access to that interface, alongside updating DSM. Remote administration should not mean exposing a device’s control panel to the public internet. Use an approved, restricted access path instead, and review network rules for any appliance that has been exposed. (BleepingComputer’s report)

Finally, check for signs that a device may already have been affected before treating patching as the whole response. The warning concerns active attacks, and reports from customers described encrypted files and ransom demands. If you find evidence of encryption or unauthorized access, preserve relevant records and follow your organization’s incident-response process rather than assuming a software update alone resolves the incident. (BleepingComputer’s report)

What victims have reported about C3RB3R

BleepingComputer described reports from Synology customers whose data had been encrypted. Reported indicators included a ransom note named read-me3.txt and the .L0CK3D extension added to encrypted files. The note demanded payment for a tool called “C3rb3r Decryptor” and offered to decrypt one file as a demonstration. These indicators are reported by the publication; they are not a vendor-confirmed signature. (BleepingComputer’s report)

These details can help administrators recognize reports associated with this campaign, but they should not be treated as a complete detection rule or proof that every affected device shares the same indicators. A ransom note’s claims are part of the attackers’ demand, not independent assurance that a purchased decryptor will work. Organizations should use their established recovery and escalation procedures and avoid making hurried payment decisions based solely on the note.

The malware name also needs a little care. BleepingComputer says this C3RB3R, also called Cerber or CerberImposter, borrowed its name from an older Cerber ransomware-as-a-service operation that emerged in 2016. The older operation and the current NAS-focused attacks are not the same event. The publication also notes that C3RB3R was previously deployed against Atlassian Confluence and GitLab servers in attacks involving vulnerabilities in those products. That history gives context, not evidence that those earlier intrusion paths apply to Synology devices. (BleepingComputer’s report)

Exposure is not the same as compromise

BleepingComputer cited Shadowserver as tracking more than 380,000 internet-exposed Synology NAS devices, while noting that the figure does not show how many have been secured or are honeypots. Treat it as a measure of observed exposure, not a count of compromised systems. (BleepingComputer’s report)

A practical closeout checklist

For each Synology NAS, record the DSM branch and current release, compare it with the fixed version applicable to that branch, and document the update. Confirm that automatic updates are enabled where appropriate. Verify that the management web interface is blocked from direct internet access, and inspect available incident signals for encrypted files or ransom notes.

Then make ownership visible. Put the device and its patch status into the organization’s asset and vulnerability-management process, and set a clear follow-up for any appliance that cannot be updated immediately. That is the unglamorous work that turns a vendor warning into risk reduction.

The current reporting leaves an important question unanswered: which vulnerability, if any, is being used in these attacks? Don’t wait for that answer to take the actions Synology has already recommended. Update the device, limit exposure, and verify the result.

Source

BleepingComputer’s report on Synology’s C3RB3R warning covers Synology’s update recommendations, the unresolved exploitation question and its referral to the November 2024 advisory, the reported fixed DSM releases, management-interface exposure guidance, victim-reported indicators, C3RB3R naming and history, and the Shadowserver exposure figure.

synology urges dsm upgrades amid c3rb3r attackssynology urges dsm upgrades amid c3rb3r attacks

synology urges dsm upgrades amid c3rb3r attackssynology urges dsm upgrades amid c3rb3r attacks

Editorial image of network-storage security: a secure server rack withEditorial image of network-storage security: a secure server rack with