DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

If at first you don’t succeed, screw it up again?

Posted on December 18, 2023 by Dissent

In mid-November, DataBreaches reported that AlphV threat actors had added MeridianLink to their leak site. When their victim wouldn’t pay them, AlphV (aka “BlackCat”)  filed a complaint with the Securities & Exchange Commission alleging that MeridianLink failed to comply with the SEC’s new cybersecurity rule requiring notification within four days of discovering a material breach.

Unfortunately for AlphV, they did not seem to know that the law wasn’t in effect yet.

Today, BlackCat tried again. Their leak site now lists Viking Therapeutics as a victim. Instead of providing any proof of claims, however, they posted that they got (translated: intimidated) a Viking Therapeutics (VT) employee to file an  SEC report on his own company:

Despite the stringent cybersecurity disclosure requirements set forth by the Securities and Exchange Commission (SEC), Viking Therapeutics failed to promptly report a material cybersecurity incident involving patient data as mandated. To address the new criteria for a persons reporting an incident, an employee of Viking Therapeutics has agreed to file a report after a productive talk with his family. Complaint details are below:

The employee’s complaint alleges that the firm violated the 4-day reporting deadline, stating in relevant part:

I hope this message finds you well. I am writing to bring to your attention a matter of significant concern regarding the failure of our company, Viking Therapeutics, to file a required cybersecurity incident report within the stipulated timeframe. As an employee deeply committed to compliance and transparency, I feel obligated to inform you that Viking Therapeutics has not fulfilled its obligation to report a material cybersecurity incident involving patient data. This omission is particularly alarming considering the potential impact on our stakeholders and investors. The incident in question involves a breach of patient data, which, to my knowledge, constitutes material information.

If AlphV’s post is truthful in claiming that an employee filed the complaint, it appears to have been under duress.

AlphV also claims that the incident has already been reported to HHS:

As it is unlikely that this organization will notify the HHS in regards to the breach of patient data, within the 60 days time-frame, we have already done so. In the event we do not receive contact within 48 hours, the data will be published in its’ entirety. After closer examination of the data, the SEC has also been informed regarding the misleading of investors due to discrepancies in published trial outcomes to shareholders

According to the affiliate involved in this incident, the attack occurred six days ago.  But when DataBreaches later requested proof of receipt from the SEC and asked for clarification as to what AlphV was calling a misleading discrepancy in published trial outcomes, there were no replies.

Once again, the attempt to invoke the SEC cybersecurity reporting rule fails, as the rule first went into effect today. As Hunton Andrews Kurth explains (emphasis added by DataBreaches):

… the U.S. Securities and Exchange Commission’s (“SEC”) new Form 8-K rules for reporting material cybersecurity incidents take effect today, December 18, for filers other than smaller reporting companies. The new rules require reporting to the SEC within four business days from the determination of materiality.

[…]

Compliance Dates. The Form 8-K and 6-K reporting requirement will take effect for cyber incidents occurring on or after December 18, 2023, though smaller reporting companies will have a delay until June 15, 2024. These dates may slip further if there is any undue delay in publishing the final rules in the Federal Register. The annual reporting requirement on Form 10-K or 20-F will take effect for fiscal years ending on or after December 15, 2023. Thus, annual reports published in 2024 will generally require the inclusion of the new Item 106 disclosure.

Whether the Viking Therapeutics employee knew there was no requirement to report this incident to the SEC but was just so scared that they submitted it, or whether AlphV’s claims are just total lies is unknown to DataBreaches.

DataBreaches did reach out to Viking Therapeutics, sending an email inquiry to a few of their executives. The email was clear that DataBreaches knows they had no obligation to report to the SEC under the new rule, but asked what they were doing in response to the alleged incident.

No reply has been received.

DataBreaches made no attempt to contact HHS at this time.

So far, then, all we have is an unconfirmed alleged breach.

DataBreaches will update this post if more information becomes available.


Related:

  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • Attorney General James Announces Settlement with Wojeski & Company Accounting Firm
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • Hackers Say They Have Personal Data of Thousands of NSA and Other Government Officials
  • UK: 'Catastrophic' attack as Russians hack files on EIGHT MoD bases and post them on the dark web
Category: Breach IncidentsHackHealth DataU.S.

Post navigation

← Troubling attacks on medical sector continue: cancer center’s data leaked, specialty infusion pharmacies locked?
Four Held in ICMR Data Leak Case →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.