Skip to main content
    Healthcare Billing Vendor Breach

    AMCA, Quest and LabCorp Healthcare Vendor Breach (2019)

    Breach Year

    2019

    Breach Type

    Healthcare Billing Vendor Breach

    TPRM Lesson

    A billing vendor can quietly hold millions of sensitive records.

    What was the AMCA, Quest and LabCorp Healthcare Vendor Breach breach?

    The AMCA breach was a 2019 incident in which American Medical Collection Agency, a third-party medical billing collections vendor, was compromised for roughly eight months between August 2018 and March 2019. The exposure included more than 25 million patient records from Quest Diagnostics, LabCorp, BioReference Laboratories, and other healthcare clients. AMCA's parent company filed for Chapter 11 bankruptcy weeks after disclosure.

    Most of the people whose data was stolen had never heard of American Medical Collection Agency. They had given blood for a routine lab test at Quest Diagnostics or LabCorp years earlier and assumed that was the end of the relationship.

    It was not. The unpaid co-pay, the small outstanding balance, the routine collections workflow that every US healthcare provider eventually outsources had quietly funnelled their name, address, date of birth, Social Security number, bank account, credit card, and in some cases lab order metadata into a billing vendor's web payment portal. That portal sat unmonitored, with an intruder inside it, for roughly eight months.

    When the disclosures landed in May and June 2019, three publicly traded healthcare giants had to explain to the market why a small billing vendor they had outsourced to was now their largest cyber incident. Within weeks, AMCA's parent company had filed for bankruptcy. The vendor was gone. The data was still out there.

    What Was It?

    American Medical Collection Agency, known as AMCA, was a third-party medical billing collections vendor operated by Retrieval-Masters Creditors Bureau, Inc. It handled overdue balances for a long list of US healthcare providers and lab networks. Patients interacted with AMCA only when a small unpaid balance was passed to collections, often through a web payment portal that accepted credit cards and bank account information.

    To do that work, AMCA had to receive and store sensitive patient and financial data: names, addresses, dates of birth, phone numbers, Social Security numbers in many cases, payment card data, and metadata about the original healthcare service. For some clients this also included references to lab tests and providers, which under HIPAA can constitute protected health information.

    AMCA was a back-office vendor of vendors. Patients did not know about it. Investors did not know about it. Most board members at Quest, LabCorp, and BioReference had never seen the contract.

    What Happened?

    Based on public reporting from SEC 8-K filings by Quest Diagnostics, LabCorp, and Opko Health (BioReference's parent), the US Department of Health and Human Services Office for Civil Rights breach portal, court filings in the AMCA bankruptcy proceedings, and reputable cybersecurity research, the publicly reported timeline runs roughly as follows.

    Initial compromise, approximately August 2018.An unauthorized actor gained access to AMCA's web payment portal infrastructure. Public reporting indicates the access persisted until roughly March 2019.

    Detection. AMCA was notified of suspicious activity tied to payment cards processed through its portal, reportedly through banking and security industry channels.

    Notification to clients, March to April 2019.AMCA notified its healthcare clients of the incident and began providing impact data to each one.

    Public disclosures, May and June 2019. Quest Diagnostics filed an 8-K on 3 June 2019 disclosing exposure of approximately 11.9 million Quest patients. LabCorp disclosed approximately 7.7 million the next day. Opko Health/BioReference disclosed approximately 422,000 initially, later revised upward. Additional smaller clients made disclosures over the following weeks. Aggregate exposure climbed past 25 million records.

    AMCA parent files for Chapter 11, June 2019.Retrieval-Masters Creditors Bureau filed for Chapter 11 bankruptcy protection on 17 June 2019, citing the cost of notification, response, and lost client business after the disclosures.

    Regulatory and legal consequences. US state attorneys general opened multi-state investigations. A 2021 multi-state settlement included a 21 million US dollar amount to be paid by AMCA, with restrictions on its operating practices going forward. Quest, LabCorp, and BioReference faced class actions and additional regulatory scrutiny in their own right.

    How Did It Happen Technically?

    In plain English: an attacker got into AMCA's web payment portal, sat there for roughly eight months, and harvested patient and payment data as it flowed through. AMCA did not detect the intrusion on its own. The detection came from banking and payment industry signals.

    Public reporting on the precise technical attack chain at AMCA is limited and was largely overtaken by the bankruptcy. From the available disclosures and the broader pattern of similar web-portal compromises in this period, the relevant elements include:

    • Compromise of a web payment portal. The entry surface was AMCA's internet-facing payment portal, which accepted patient identifiers and payment data. Exposure persisted for roughly eight months.
    • Long dwell time. Whatever the initial vulnerability, the more important failure was the lack of detection. Eight months of unauthorized access to a system processing payment card data and PHI is a structural monitoring failure.
    • Sensitive data concentrated in one place.The portal received and held data from multiple major healthcare clients, which made one compromise sufficient to affect millions of patients across providers.
    • External detection. Detection occurred not through AMCA's own monitoring but through industry channels tied to payment card abuse, which is a recurring pattern in third-party billing compromises.

    The technical and operational control failures that mattered most:

    • Limited security investment relative to the volume and sensitivity of data processed.
    • Inadequate monitoring and detection on the payment portal.
    • Excessive retention of patient and payment data inside the vendor environment.
    • Customer-side TPRM that assessed paperwork (SOC 2, PCI attestations) but did not test operational controls.
    • No timely or structured incident notification flow back to the healthcare clients.

    No exploit code is included here. The defensive lesson is more useful than the offensive one.

    Why This Was a TPRM Failure

    AMCA was the canonical example of a low-visibility billing vendor producing a strategic third-party breach for the largest names on its client list.

    • Vendor criticality was scored on the wrong factors.AMCA processed a small share of revenue but held PHI and payment data for tens of millions of patients. Its criticality from a data exposure perspective was extreme. Its criticality on most TPRM scorecards was not.
    • Data concentration was unmanaged. Quest, LabCorp, and BioReference all sent collections data to AMCA. Concentration risk in the billing collections vertical was effectively national in scale, with no industry-level concentration map.
    • Questionnaires measured paperwork, not operations.SOC 2 reports and PCI attestations were the standard of assurance. They did not surface the actual operating posture of the payment portal.
    • Notification SLAs were too slow. The dwell time was eight months. The notification to healthcare clients was slow enough that affected patients learned months after exposure had ended.
    • Retention was not contractually limited.Patient and payment data lived inside the vendor longer than the business reason required, increasing the population affected once a compromise occurred.
    • Vendor financial resilience was not assessed.AMCA filed for bankruptcy within weeks of disclosure. That outcome left the healthcare clients to absorb most of the practical response cost and reputational damage.
    • Subcontractor and downstream vendors were invisible to patients.Patients had no awareness that a billing vendor existed between them and the lab. The trust chain was longer than they had agreed to.

    Business Impact

    The AMCA incident produced one of the highest-profile business-associate breaches in HIPAA history at the time.

    For AMCA and its parent. Retrieval-Masters Creditors Bureau filed for Chapter 11 bankruptcy on 17 June 2019, citing notification costs, lost client business, and response expenses. AMCA effectively did not survive the incident as a viable entity.

    For the major clients. Specific consequences included:

    • Quest Diagnostics: approximately 11.9 million patients affected; multi-state regulatory action and class action exposure.
    • LabCorp: approximately 7.7 million patients affected; parallel regulatory action and class action exposure.
    • Opko Health/BioReference Laboratories: approximately 422,000 patients initially, revised upward over time.
    • Additional smaller healthcare and clinical clients made parallel disclosures, with aggregate exposure climbing above 25 million records.
    • Multi-state attorney general investigation culminating in a 2021 settlement.
    • Sustained class action litigation in multiple jurisdictions.
    • Long-term increase in regulatory and customer expectations for business associate cybersecurity in US healthcare.

    Consequences

    AMCA reshaped how US healthcare boards and regulators view business associate risk.

    • HHS Office for Civil Rights elevated the visibility of business associate breaches and continued to enforce HIPAA against both covered entities and business associates.
    • A multi-state attorney general settlement in 2021 imposed a 21 million US dollar amount on AMCA, along with practice restrictions, after the entity emerged from bankruptcy.
    • Healthcare providers reassessed billing collections relationships and increased due diligence on data retention, monitoring, and incident response.
    • SEC scrutiny of cyber disclosure timeliness, which culminated in the 2023 SEC rules on cybersecurity disclosure, was informed in part by incidents like AMCA.
    • Industry awareness of the gap between SOC 2 paperwork and operational reality increased materially, even though closing that gap remains an open challenge.

    Some consequences are confirmed and measurable. Others, such as the long-term shift in business associate contracting and the legal precedent on vendor financial resilience, continue to evolve.

    Practical Learnings for TPRM Teams

    1. Score vendors on data exposure, not on spend. A small billing vendor holding tens of millions of patient records is a tier-one third party.
    2. Inventory every back-office vendor that touches regulated data, including collections, billing, claims processing, and print and mail.
    3. Test operational controls, not just paperwork. Validate monitoring, patching, MFA, and detection at critical vendors.
    4. Require strict retention limits in contracts. Files that no longer exist cannot be stolen.
    5. Define notification SLAs in hours, not months, and rehearse them with critical vendors.
    6. Assess vendor financial resilience. A vendor that cannot survive disclosure is not a vendor you can rely on for incident response.
    7. Require third-party detection capabilities and accept evidence of independent monitoring, not just policy.
    8. Map data flow from your environment into the vendor, into any sub-processor, and back out. Patients deserve to know who holds their data.
    9. Pre-build patient and regulator communication templates for business associate breaches.
    10. Put back-office vendor concentration on the board agenda, especially in healthcare and financial services.

    Technical Protection Checklist

    A. Identity and Access

    • Require phishing-resistant MFA on all administrative access at billing and collections vendors.
    • Apply least privilege to vendor staff accounts.
    • Remove shared accounts on internet-exposed vendor portals.
    • Monitor for new accounts and abnormal session activity on vendor systems.

    B. Web Portal and Application Security

    • Apply web application firewalls and tuned anomaly detection on payment portals.
    • Maintain a vulnerability management program with a defined patch SLA for internet-exposed components.
    • Restrict and monitor file uploads and form submissions.
    • Run independent penetration testing on payment portals annually at minimum.

    C. Data Protection

    • Minimize the data sent to billing and collections vendors to the field set strictly required.
    • Define and enforce retention limits in contracts.
    • Encrypt sensitive data both at rest and in transit.
    • Tokenize payment card data wherever possible.
    • Restrict and monitor mass export.

    D. Monitoring and Detection

    • Require vendors to maintain 24x7 detection capability with defined response SLAs.
    • Receive vendor security telemetry where contractually possible.
    • Use industry payment-card abuse intelligence to detect compromised vendors early.
    • Audit vendor logs for evidence of dwell time on a defined cadence.

    E. Vendor Financial and Operational Resilience

    • Assess vendor financial resilience and incident-survivability.
    • Require evidence of cyber insurance and incident response retainers.
    • Define exit and substitution plans for tier-one back-office vendors.

    F. Vendor Incident Response

    • Maintain up-to-date contacts at billing and collections vendors.
    • Define notification timelines in writing.
    • Pre-map systems and data exposed by each back-office vendor.
    • Prepare patient, regulator, and board communication templates in advance.

    G. Fourth-Party Risk

    • Ask billing vendors who their sub-processors are.
    • Identify any downstream vendor handling regulated data on their behalf.
    • Require disclosure of material fourth parties in contracts.

    H. Board and Executive Reporting

    • Track back-office vendor count and the data classes they hold.
    • Report concentration risk in billing and collections separately from operational vendors.
    • Translate vendor risk into patient impact and regulatory exposure for leadership.

    What Most People Miss About This Breach

    Most summaries describe AMCA as a billing-vendor breach. That is true but it understates the structural lesson.

    The first thing people miss is the dwell time. The portal was compromised for roughly eight months. The breach was not primarily a technical sophistication story. It was a monitoring story. AMCA simply did not have the operational capability to notice an intruder camping inside its core customer-facing system.

    The second thing people miss is the financial resilience issue. AMCA filed for bankruptcy weeks after disclosure. That outcome should be treated as one of the most important TPRM signals of the decade: a critical vendor that cannot survive its own incident is not a vendor that can help you respond to it.

    The third thing people miss is the patient experience. The people whose data was stolen had no relationship with AMCA. They had a relationship with Quest, LabCorp, or BioReference. The breach travelled one relationship further than they had agreed to, and the apology had to come from the brand they knew, not the vendor that lost the data.

    Final TPRM Takeaway

    A billing vendor can quietly hold millions of sensitive records, remain compromised for the better part of a year, and disappear into bankruptcy weeks after disclosure. AMCA was the moment US healthcare learned that back-office third parties holding regulated data are tier-one risks, that paperwork is not a control, and that the patient does not care which vendor lost the data. They will hold the brand they trusted accountable.

    Frequently Asked Questions

    What was the AMCA breach?

    The AMCA breach was a 2018 to 2019 incident in which American Medical Collection Agency, a third-party medical billing collections vendor operated by Retrieval-Masters Creditors Bureau, was compromised for roughly eight months. The exposure ultimately included more than 25 million patient records from Quest Diagnostics, LabCorp, BioReference Laboratories, and other clients.

    Why is AMCA considered a third-party breach?

    Patients did not have a relationship with AMCA. They had a relationship with their lab provider. AMCA was a business associate processing collections on behalf of healthcare providers under HIPAA, and the breach originated inside the vendor environment, making it a defining example of a third-party business associate breach.

    How did the AMCA breach happen?

    An unauthorized actor accessed AMCA's web payment portal in roughly August 2018 and persisted until approximately March 2019. Public reporting on the precise attack chain is limited, but the relevant control failures included inadequate monitoring and detection, long dwell time, excessive retention, and reliance on external industry signals rather than internal detection.

    What was the business impact of the AMCA breach?

    AMCA's parent company, Retrieval-Masters Creditors Bureau, filed for Chapter 11 bankruptcy weeks after disclosure. Quest Diagnostics, LabCorp, and BioReference Laboratories all filed 8-K disclosures, with aggregate exposure climbing above 25 million records. A 2021 multi-state attorney general settlement imposed a 21 million US dollar amount on AMCA with practice restrictions.

    What should TPRM teams learn from AMCA?

    Score vendors on data exposure not spend, test operational controls not just paperwork, require strict retention limits, assess vendor financial resilience, define notification SLAs in hours, map data flow including sub-processors, and put back-office vendor concentration on the board agenda.

    How can organizations reduce this type of third-party risk?

    Inventory every back-office vendor that touches regulated data, require evidence-based assurance rather than paperwork, minimize the data sent to vendors, tokenize payment data, demand 24x7 detection capability with response SLAs, and prepare exit and substitution plans for tier-one back-office vendors.

    What technical controls would have helped during AMCA?

    Tuned web application firewalls and anomaly detection on the payment portal, strong vulnerability management, MFA on all administrative access, robust monitoring with realistic detection SLAs, payment card tokenization, and minimization of stored data would each have materially reduced exposure.

    What is the biggest lesson from AMCA?

    A billing vendor can quietly hold millions of sensitive records, remain compromised for the better part of a year, and collapse into bankruptcy weeks after disclosure. Back-office third parties that handle regulated data are tier-one risks regardless of contract value, and the patient will always hold the brand they trusted accountable.

    TPRM Blog

    Related TPRM analysis from the blog

    Continue learning with the latest breach alerts, regulatory updates, and analyst playbooks from blog.learntprm.com.

    Visit blog.learntprm.com
    Safe Security - founding sponsor of LearnTPRM.comFounding Sponsor
    For CISOs, TPRM leads and vendor risk program owners

    Autonomous TPRM. 90% less manual effort.

    Almost every case here was findable before it happened

    Read enough third-party breaches and the pattern is brutal: an undisclosed fourth party, an expired certification, an exposure that sat on the internet for weeks. Nobody was lazy - the signals simply arrive faster than a human review cycle. The SAFE TPRM AI Co-Worker watches for them continuously.

    This is for you if you own a third-party risk program - roughly 100+ vendors, quarterly reassessments, DORA / NIS2 / OCC pressure and no new headcount coming. The link opens Safe Security's platform page, not a gated form.

    Five correlated data dimensions per vendor, refreshed continuously across the whole portfolio.

    Zero-touch due diligenceContinuous monitoring across 5 dimensionsAI-powered risk scoring workflows
    • The Fourth-Party Discovery agent finds the undisclosed downstream provider before it becomes your incident.
    • The Outside-In agent detects new vulnerabilities, misconfigurations and breaches as they surface.
    • The Threat Intel agent tracks leaked credentials, filings and legal events per vendor.
    Evaluate SAFE for my organization

    For security and risk leaders assessing a TPRM platform. Opens safe.security in a new tab.

    25+

    AI agents

    90%

    Less manual effort

    None

    Additional headcount

    200+

    Organizations globally

    End to end

    Intake to offboarding

    Ready to Prove You're a TPRM Warrior?

    Most people talk about risk management. Few can prove their expertise under pressure.

    Start Your Free Certification