[LYNX] – Ransomware Victim: saacke[.]com

image

NOTE: No files or stolen information are exfiltrated, downloaded, taken, hosted, seen, reposted, or disclosed by RedPacket Security. Any legal issues relating to the content should be directed at the attackers, not RedPacket Security. This blog is an editorial notice informing that a company has fallen victim to a ransomware attack. RedPacket Security is not affiliated with any ransomware threat actors or groups and will not host infringing content. The information on this page is automated and redacted whilst being scraped directly from the LYNX Onion Dark Web Tor Blog page.

Ransomware group:
LYNX
Victim name:
SAACKE[.]COM

AI Generated Summary of the Ransomware Leak Page

On 2025-10-20 14:30:41.976000, a leak post associated with the Lynx group appeared for the victim saacke.com. The domain corresponds to SAACKE GmbH, a German manufacturing company founded in 1931 and headquartered in Bremen. SAACKE specializes in high‑efficiency combustion and thermal energy systems for industrial and marine applications, including burners, boilers, and complete heating solutions focused on energy efficiency, emission reductions, and the use of alternative fuels. The post does not provide a specific compromise date; the timestamp should be treated as the post date. The page does not explicitly state whether the incident involved encryption or a data leak, nor does it reveal any ransom demand or amount in the visible text. A claim URL indicator appears present on the leak page, but no substantive claim details are shown here. There are no screenshots, images, or downloadable files included in the excerpt.

From a sanitization and risk-communication perspective, the content remains a neutral English rendition of the victim’s corporate profile with no personal data or contact details present to redact. There are no other company names to highlight beyond the victim, and the excerpt contains no PII, emails, or addresses to redact. The page includes no visible images or attachments; the only external cue is a claim URL indicator, suggesting there may be additional information behind a link, though such content is not included in this excerpt. The post date stands as the sole temporal marker, and, due to the lack of explicit compromise details, cannot be confirmed as the actual breach date.

Support Our Work

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.

AI APIs OSINT driven New features