LiveBreach Intelligence: data breaches, leaks & ransomware, tracked as they surface
Recent BreachesData breach tracker

Recent Breaches › B. Riley Financial, Inc Discloses Material Cybersecurity Incident (SEC 8-K)

HIGH severityConfirmedHow we verify

B. Riley Financial, Inc Discloses Material Cybersecurity Incident (SEC 8-K): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·April 5, 2024
B. Riley Financial, Inc Discloses Material Cybersecurity Incident (SEC 8-K)

Reported April 5, 2024. Approximately disclosed in filing people affected.

HIGH
Severity
disclosed in filing
People affected
1
Data types exposed
April 5, 2024
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The B. Riley Financial, Inc Discloses Material Cybersecurity Incident (SEC 8-K) (reported April 5, 2024) exposed Material cybersecurity incident (per SEC 8-K Item 1.05) belonging to roughly disclosed in filing people. If you have an account with them, your information may now be circulating on the open web and with data brokers. Here’s exactly what happened, how to check if you were affected, and what to do next.

Severity & verification
HIGH severityConfirmed
Data types not itemised.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the B. Riley Financial, Inc Discloses Material Cybersecurity Incident (SEC 8-K) breach?
disclosed in filing accounts were exposed here. See if yours is one — and every other breach it’s in. 15-sec check, no card.

In a threat landscape where financial-services firms and their operating subsidiaries remain frequent targets for unauthorized network access, public companies increasingly use SEC Form 8-K filings under Item 1.05 to notify investors of material cybersecurity incidents. On 5 April 2024 B. Riley Financial, Inc. made such a disclosure concerning its indirect subsidiary Targus International, LLC and certain affiliates.

The filing states that a threat actor gained unauthorized access to certain of Targus’ file systems. Because the incident was judged material, the parent company reported it promptly. Public detail remains limited to the facts set out in the 8-K; the precise scale, full data categories and final impact have not been elaborated beyond that filing.

Breaking down the breach

According to the SEC 8-K filed on 5 April 2024, Targus International, LLC and certain affiliates—each an indirect subsidiary of B. Riley Financial, Inc.—discovered on that same date that a threat actor had obtained unauthorized access to certain of Targus’ file systems. Upon discovery, and with assistance from external cybersecurity counsel and consultants, Targus immediately activated its incident-response and business-continuity protocols to investigate, contain and remediate the incident. The filing notes that proactive containment measures taken to disrupt the unauthorized access resulted in (the public summary ends at this point). The number of people affected is described as disclosed in the filing, yet no specific headcount appears in the available extract. No further technical method, duration of access or complete inventory of affected systems is provided in the public record.

How a breach like this happens

Incidents involving unauthorized access to corporate file systems typically begin with an initial foothold—often obtained through compromised credentials, phishing, exploitation of an unpatched remote-access service, or a vulnerable third-party application. Once inside, an attacker may move laterally, locate shared drives or document repositories, and copy or encrypt data. Detection can occur through anomalous authentication logs, endpoint alerts or employee reports. Containment usually involves isolating affected hosts, resetting credentials, blocking command-and-control channels and restoring systems from known-good backups. Because no specific threat group is named in the B. Riley filing, the above description remains a general account of how such events commonly unfold rather than a reconstruction of this particular case.

B. Riley Financial, Inc and its sector

B. Riley Financial, Inc. is a publicly traded diversified financial-services company that provides investment banking, wealth management, restructuring advisory and related services. Through acquisitions it also holds operating subsidiaries in other industries; Targus International, LLC is one such subsidiary, historically associated with computer accessories and related commercial operations. Financial-services organizations and their affiliates routinely maintain customer records, employee data, transaction histories, contracts and proprietary business documents. A material cybersecurity incident at any subsidiary can therefore raise questions about the confidentiality of those records, the continuity of operations and potential regulatory or contractual obligations that flow back to the parent company.

The information in question

The 8-K characterizes the event as a material cybersecurity incident involving unauthorized access to certain Targus file systems. No specific data categories—such as names, Social Security numbers, financial account details or intellectual property—are enumerated in the public summary. Organizations of this type commonly store customer contact information, employee personnel files, supplier contracts and internal financial records on shared file systems. Because the exact contents remain unconfirmed beyond the filing’s general description, it is not possible to state with certainty which of those typical data types, if any, were exposed.

What's at stake

For individuals whose information may have been present on the accessed systems, the principal risks include potential identity theft, phishing campaigns that leverage leaked personal details, and unauthorized use of financial or employment data. For B. Riley Financial and Targus the stakes include operational disruption during containment, possible notification and remediation costs, reputational impact with clients and partners, and any regulatory scrutiny that follows a material incident disclosure. Because the filing does not quantify the number of affected persons or the precise data elements, the concrete scope of these risks cannot be measured from public sources alone.

What to do if you're exposed

If you believe your information may have been involved, take the following practical steps:

Readers can also run a free exposure scan of their email address to check whether their information has already surfaced in known breach data sets. Public detail on this incident remains limited to the SEC 8-K; further clarity will depend on any subsequent disclosures the company elects to make.

AICompiled with AI assistance from public sources and published under our editorial standards.

Editorial & sourcing policy
Recent Breaches is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data, and we do not hold the data claimed in leak-site listings. Incidents are compiled from publicly accessible sources and threat-intelligence platforms and are reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — write to support@galaxywarden.com or press@recentbreaches.com.
Check if you’re exposed →

How this breach connects

Company

Method

CompanyB. Riley Financial, Inc security record
74/100
DoxxScan™ · Moderate doxx risk
B- 77Above-average record

1 reported incident on record.

See B. Riley Financial, Inc’s full breach history →

More recent breaches

Brandywine Realty Trust Discloses Material Cybersecurity Incident (SEC 8-K)May 1, 2024Federal Home Loan Bank of New York Discloses Material Cybersecurity Incident (SEC 8-K)February 21, 2024SouthState Discloses Material Cybersecurity Incident (SEC 8-K)February 6, 2024Navient Discloses Material Cybersecurity Incident (SEC 8-K)June 29, 2026

Latest breaches

Read GalaxyWarden’s full analysis of the B. Riley Financial, Inc Discloses Material Cybersecurity Incident (SEC 8-K) →

Source: SEC EDGAR Form 8-K (Item 1.05)

Verified breach

Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.

Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.

ShareXLinkedInFacebookRedditWhatsAppTelegram