Back Redpacketsecurity [SILENTRANSOMGROUP] – Ransomware Victim: B[.][.][.]
Verification alert Listings attributed to SILENTRANSOMGROUP have been reported as including unverified or fabricated victim claims. Treat this post as unconfirmed until corroborated with independent evidence. See further information here: BankInfoSecurity
See further information here: BankInfoSecurity
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 SILENTRANSOMGROUP Onion Dark Web Tor Blog page.
AI Generated Summary of the Ransomware Leak Page
On September 22, 2026, the ransomware group SilentRansomGroup listed B… on its leak site. No industry or country information was provided for the victim, and the entry does not identify a specific compromise date; therefore, September 22, 2026, is treated as the post date. The listing is marked as a redacted entry, with the full company name reportedly pending disclosure while a “full data” countdown is active. The available post does not specify whether B… experienced systems encryption, data exfiltration, or another form of impact. It also provides no ransom demand, stolen-data volume, or details the allegedly compromised information. No screenshots or other images are included, and no downloadable files are indicated. The presence of a claim-page reference suggests that additional information may become available when the disclosure timer expires.
On September 22, 2026, the ransomware group SilentRansomGroup listed B… on its leak site. No industry or country information was provided for the victim, and the entry does not identify a specific compromise date; therefore, September 22, 2026, is treated as the post date. The listing is marked as a redacted entry, with the full company name reportedly pending disclosure while a “full data” countdown is active.
The available post does not specify whether B… experienced systems encryption, data exfiltration, or another form of impact. It also provides no ransom demand, stolen-data volume, or details the allegedly compromised information. No screenshots or other images are included, and no downloadable files are indicated. The presence of a claim-page reference suggests that additional information may become available when the disclosure timer expires.
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.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
