Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

Medical IT Contractor Folds After Breaches

Blamed for privacy breaches at five different hospitals, Verus Inc. silently closes its doors

Verus Inc., the IT contractor that has been implicated in security breaches at at least five different hospitals across the country, has gone out of business.

The Bellevue, Wash., company, which built and maintained Websites and services on behalf of some 40 to 60 hospitals nationwide, was disbanded "eight to 10 weeks ago" when investors pulled the plug following a massive blunder that exposed many of its clients' data to the outside world, according to an executive at MedSeek, an IT contractor that is now handling many of Verus' clients.

While reports of the breaches have been issued in dribs and drabs, all of the data losses can now be attributed to a single incident, in which Verus employees left a firewall down following the transfer of data from one server to another, according to David Levin, vice president of marketing at MedSeek.

"All of the breaches were the result of an IT error, as opposed to any problems with the software," Levin says. "They made a huge mistake, and it literally shut the company down. It's really a cautionary tale."

Verus's Website has been pulled down, and calls to the company's offices are referred to MedSeek customer service. No announcement of the shutdown, nor any explanation of the reasons behind it, appear to have been issued to the media or to Verus partners.

"We're not sure if the breaches were the only reason why they closed down -- there might have been other issues as well," Levin says. "But we know we got the call to support the [Verus] customers very soon after the breach was supposed to have happened."

Reports of the breaches range from mid-April to late May, but Verus has been implicated in at least five disclosures since the beginning of June:

  • On June 4, Stevens Hospital in Edmonds, Wash., reported the exposure of 550 patients' data through a failure in the online bill payment service operated by Verus.

  • On June 6, Keenewick General Hospital in Washington reported a similar breach affecting 1,000 patients, and attributed it to the Verus online bill payment service.

  • On June 7, Concord Hospital in New Hampshire disclosed the loss of 9,000 names because Verus had "turned off a firewall for maintenance purposes" and failed to turn it back on again. The breach was not disclosed publicly until late July (See Third Parties Fumble Data Handoffs.)

  • On July 24, St. Vincent's Hospital in Indiana reported a security breach that exposed data on some 51,000 patients. The hospital blamed Verus, which exposed the data while transferring data between servers.

  • Earlier today, Sky Lakes Medical Center in Oregon revealed that 30,000 patients' names had been inadvertently exposed in late May, when Verus didn't take sufficient precautions while transferring data from one server to another.

All of the hospitals said they immediately terminated their contracts with Verus following the breach. All of the hospitals said they have yet to see any reports of hackers or criminals using the data.

According to Levin, the breaches all affected hospitals using Verus's VPAC online billing system, which MedSeek does not use. Verus's hospital customers will be given a choice as to whether they want to migrate to the MedSeek platform and services, or move to some other vendor.

Have a comment on this story? Please click "Discuss" at the top of this page. If you'd like to contact Dark Reading's editors directly, send us a message.

Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
7 Old IT Things Every New InfoSec Pro Should Know
Joan Goodchild, Staff Editor,  4/20/2021
News
Cloud-Native Businesses Struggle With Security
Robert Lemos, Contributing Writer,  5/6/2021
Commentary
Defending Against Web Scraping Attacks
Rob Simon, Principal Security Consultant at TrustedSec,  5/7/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-31922
PUBLISHED: 2021-05-14
An HTTP Request Smuggling vulnerability in Pulse Secure Virtual Traffic Manager before 21.1 could allow an attacker to smuggle an HTTP request through an HTTP/2 Header. This vulnerability is resolved in 21.1, 20.3R1, 20.2R1, 20.1R2, 19.2R4, and 18.2R3.
CVE-2021-32051
PUBLISHED: 2021-05-14
Hexagon G!nius Auskunftsportal before 5.0.0.0 allows SQL injection via the GiPWorkflow/Service/DownloadPublicFile id parameter.
CVE-2021-32615
PUBLISHED: 2021-05-13
Piwigo 11.4.0 allows admin/user_list_backend.php order[0][dir] SQL Injection.
CVE-2021-33026
PUBLISHED: 2021-05-13
The Flask-Caching extension through 1.10.1 for Flask relies on Pickle for serialization, which may lead to remote code execution or local privilege escalation. If an attacker gains access to cache storage (e.g., filesystem, Memcached, Redis, etc.), they can construct a crafted payload, poison the ca...
CVE-2021-31876
PUBLISHED: 2021-05-13
Bitcoin Core 0.12.0 through 0.21.1 does not properly implement the replacement policy specified in BIP125, which makes it easier for attackers to trigger a loss of funds, or a denial of service attack against downstream projects such as Lightning network nodes. An unconfirmed child transaction with ...