Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  /

  / CMMC Certification Cost: Complete Pricing Breakdown 2026

CMMC Certification Cost: Complete Pricing Breakdown 2026

CMMC certification costs between $4,000 and $30,000 at Level 1, $30,000 to $300,000 or more at Level 2, and $100,000 to well over $1 million at Level 3. Most contractors expect the audit fee to be the big number. It isn’t. The formal assessment typically accounts for only 25% to 40% of total spend, with preparation, remediation, and technology upgrades consuming the rest.

The stakes changed in late 2025. The final 48 CFR acquisition rule took effect on November 10, 2025, which means CMMC requirements now appear directly in Department of Defense (DoD) solicitations and contracts. Starting in November 2026, Phase 2 of the rollout gives contracting officers the authority to require third-party certification for Level 2 work. If you handle Controlled Unclassified Information (CUI), certification is no longer optional, and the cost question becomes a budgeting exercise rather than a hypothetical.

This guide breaks down every major cost category, what moves your number up or down, and how to keep the total under control.

What Is CMMC Certification and Why Does Cost Vary?

The Cybersecurity Maturity Model Certification (CMMC) is the DoD’s framework for verifying that companies in the Defense Industrial Base (DIB) actually protect the sensitive information they handle. The program, codified in 32 CFR Part 170, builds on the security requirements of NIST SP 800-171 and, at the top tier, selected controls from NIST SP 800-172.

Costs vary so widely because you can’t buy CMMC off a shelf. Your environment has to reach a certain state and then stay there. A 15-person machine shop with one well-scoped CUI enclave faces a fundamentally different project than a 500-person prime contractor with CUI flowing through a dozen systems. Your starting security posture, the scope of your assessment boundary, and whether you build internally or hire help all move the total by six figures in either direction.

Let Axipro help you build a business continuity plan that's practical, compliant, and audit-ready.

Schedule Your Free Assessment Today

Average CMMC Certification Cost at a Glance

The DoD’s own published estimates are instructive. A triennial Level 2 certification assessment, including affirmations, is projected at roughly $105,000 for small entities and $118,000 for larger ones. Those figures cover only assessment and affirmation activities, though. The DoD excludes implementation costs from its estimates on the grounds that NIST SP 800-171 compliance has been contractually required under DFARS 252.204-7012 since 2017. Your real budget has to cover both.

CMMC Certification Cost

CMMC Certification Cost by Level

CMMC Level 1 (Foundational) Cost: $5,000 – $30,000

Level 1 covers Federal Contract Information (FCI) and requires 15 basic safeguarding practices drawn from FAR 52.204-21. Because Level 1 permits an annual self-assessment with no third-party auditor, the costs are internal labor, basic tooling, and documentation. Small contractors with reasonable IT hygiene often land near the bottom of the range. The DoD estimates annual Level 1 assessment and affirmation activity at around $6,000 for a small entity, with the remainder of the range driven by any remediation needed to attest honestly.

CMMC Level 2 (Advanced) Cost: $50,000 – $300,000+

Level 2 is where most of the DIB lands and where budgets get serious. It requires full implementation of all 110 security requirements in NIST SP 800-171, assessed across 320 individual objectives. For most contracts, a C3PAO (Certified Third-Party Assessor Organization) accredited by the Cyber AB has to conduct the assessment every three years.

Market data puts C3PAO assessment fees at $30,000 to $100,000 depending on scope, site count, and complexity. Preparation dwarfs that figure for most organizations. Companies starting from a low maturity baseline routinely spend three to four times the assessment fee on readiness work before an auditor ever shows up.

CMMC Level 3 (Expert) Cost: $300,000 – $1,000,000+

Level 3 adds 24 enhanced requirements from NIST SP 800-172 on top of a completed Level 2 certification, and the assessment is conducted by the government’s DIBCAC rather than a commercial C3PAO. DIBCAC charges no assessment fee, but don’t mistake free for cheap. The DoD estimated roughly $41,000 in additional implementation cost for the 800-172 controls alone, and total triennial assessment-related costs in the $146,000 to $159,000 range. Real-world totals run far higher once you account for the advanced tooling, threat hunting capability, and organizational changes Level 3 demands. Only contractors supporting the most sensitive programs need this tier.

Worth Knowing: You can't skip to Level 3.

You can't skip to Level 3. A final Level 2 certification with all POA&M items closed is a prerequisite for the same assessment scope, so Level 3 budgets always include a full Level 2 project first.

CMMC Certification Cost Breakdown by Expense Category

Gap Assessment and Readiness Planning Costs

A gap assessment maps your current environment against NIST SP 800-171 and typically costs $1,500 to $20,000 depending on depth and scope. This is the most valuable dollar you’ll spend in the entire project, because everything downstream is priced off what it finds.

Documentation and System Security Plan (SSP) Costs

The System Security Plan (SSP) is the cornerstone document of any assessment, mapping every control to your specific implementation. Professionally developed SSPs and supporting policies run $12,000 to $60,000. A weak SSP is one of the most common reasons assessments stall or fail, so this is a poor place to economize.

Remediation and Security Control Implementation Costs

Closing the gaps is usually the largest line item: $20,000 to $150,000 or more. Multi-factor authentication, logging and SIEM deployment, encryption, access control restructuring, and incident response capability all live here. Organizations with mature security postures spend far less than those starting from scratch.

Technology and Infrastructure Upgrade Costs

Many contractors move CUI into a dedicated enclave rather than securing their entire network. Enclave platforms typically cost $300 to $400 per user per month. Others upgrade endpoint protection, replace unsupported systems, or migrate to government-grade cloud environments, each with its own licensing and migration costs.

C3PAO Assessment and Audit Fees

The formal Level 2 assessment runs $30,000 to $100,000, driven by assessor-days, number of sites, and evidence quality. Well-organized evidence directly reduces assessor time and therefore your invoice.

Consulting and Advisory Fees

Specialist consultants, including Registered Practitioners (RPs) and Certified CMMC Professionals (CCPs), bill roughly $250 to $400 per hour. Engagements range from targeted advisory work to full program management. Many contractors instead retain a Managed Security Service Provider (MSSP), typically starting at $2,000 to $3,500 per month.

Staff Training and Awareness Program Costs

Security awareness training, role-based training for IT staff, and CUI handling training generally cost $2,000 to $10,000 per year. Assessors check for evidence of training, not just a policy saying it happens.

Internal Personnel and Labor Costs

The least visible cost is your own people’s time: evidence collection, interviews, remediation project management, and documentation review pull hours from billable work. Small contractors feel this hardest, with per-employee compliance costs of roughly $2,500 to $4,600 compared with $600 to $1,000 at enterprise scale.

Ongoing CMMC Costs After Certification

Annual Maintenance and Monitoring Costs

Budget $10,000 to $50,000 per year for continuous monitoring tools, vulnerability scanning, log retention, policy updates, and license renewals. Certification reflects a point in time. Your contractual obligation to stay compliant doesn’t expire between assessments.

Recertification Costs (Every 3 Years)

Level 2 certification lasts three years, after which the full C3PAO assessment repeats. Recertification is usually cheaper than the first cycle because the environment and evidence already exist, but plan for the assessment fee plus refreshed documentation and a pre-assessment review.

Continuous Compliance and Reporting Costs

Annual affirmations by a senior official must be filed in the Supplier Performance Risk System (SPRS), and your score has to stay current. False or careless affirmations carry real legal exposure under the False Claims Act, which is why many companies fund an annual internal review before signing.

Important: The affirmation requirement changes the risk calculus entirely. An executive personally attests to compliance every year, and the Department of Justice has actively pursued False Claims Act cases over cybersecurity misrepresentations. Treat annual affirmations as a compliance event with evidence behind them rather than a formality.

Key Factors That Influence Your CMMC Certification Cost

Company Size and Number of Employees

More users mean more endpoints, more accounts, more training seats, and more assessment hours. Costs scale with headcount, though per-employee cost falls as fixed expenses spread across more staff.

Scope of Controlled Unclassified Information (CUI)

Scope is the single biggest cost driver. CUI touching every system means every system is in scope. CUI confined to a tight enclave means the assessment boundary, and the bill, shrinks accordingly.

Existing Cybersecurity Maturity and Posture

A contractor already operating close to NIST SP 800-171, perhaps with SOC 2 or ISO 27001 in place, inherits significant control overlap and spends far less on remediation than one starting cold.

Cloud vs. On-Premise Environment

Cloud environments with strong compliance inheritance, particularly FedRAMP-authorized services, reduce the number of controls you need to build yourself. Legacy on-premise infrastructure often requires expensive upgrades or segmentation.

Internal Resources vs. Outsourced Support

In-house expertise converts consulting fees into salary you already pay. Most small and mid-size contractors blend the two: internal ownership of the program, external specialists for gap assessment, SSP development, and mock audits.

Timeline and Urgency

Compressed timelines cost more. Rushed remediation means premium consulting rates, expedited procurement, and less time to optimize scope. With C3PAO capacity tightening ahead of the November 2026 Phase 2 milestone, late movers will also face scheduling backlogs.

 

Hidden and Often Overlooked CMMC Costs

Several costs rarely appear in initial budgets.

  • Flow-down requirements mean prime contractors increasingly demand proof of compliance from subcontractors before the government does, sometimes on short notice.
  • External Service Providers (ESPs) that touch your CUI can fall within your assessment scope, adding coordination and evidence-gathering work. Productivity dips during remediation, assessment scheduling delays, and re-assessment fees for failed controls all add up.
  • So does the cost of closing POA&M (Plan of Action and Milestones) items within the mandated 180-day window after a conditional certification.

Insider Note: Only 431 organizations held a final Level 2 certification as of October 2025, against roughly 80,000 companies the DoD expects to need one. That mismatch between assessor capacity and demand is a cost factor in itself. Contractors who book C3PAO slots early are already negotiating from a stronger position than those who wait for a contract clause to force the issue.

Let Axipro help you build a business continuity plan that's practical, compliant, and audit-ready.

Schedule Your Free Assessment Today

CMMC Cost Estimates for Small vs. Mid-Size vs. Large Contractors

These are first-cycle figures including preparation. Contractors with strong existing postures can land below these ranges. Those discovering years of deferred IT investment can exceed them.

How to Reduce CMMC Certification Costs

Limit and Segment Your Compliance Scope

Isolate CUI into a defined enclave with strict boundaries. Every system you keep out of scope is a system you neither remediate nor pay an assessor to examine. Scoping decisions made before remediation begins are worth more than any discount negotiated afterward.

Use a Government Community Cloud (GCC High) Environment

Microsoft 365 GCC High and comparable government cloud environments are built for CUI and ITAR data, so you inherit controls instead of building them yourself. Licensing costs more than commercial tiers, but the inherited compliance typically outweighs the premium for CUI-heavy organizations.

Use Compliance Automation Tools

Governance platforms that automate evidence collection, control monitoring, and documentation reduce both consultant hours and internal labor, and they make the triennial re-assessment much cheaper by keeping evidence current year-round.

Use Pre-Built Policy Templates and Documentation

Starting policies and the SSP from proven templates instead of a blank page cuts documentation costs substantially. Templates still require tailoring, and assessors can tell when they haven’t been, but the drafting effort drops by half or more.

Choose the Right C3PAO and Consultants

Get quotes from multiple C3PAOs listed on the Cyber AB Marketplace and compare methodology, not just price. A cheap assessor who drags out the engagement or fails controls that a readiness review would have caught costs more in the end. The same logic applies to consultants: defense-sector experience matters more than hourly rate.

Pro Tip: Ask any Prospective C3PAO

Ask any prospective C3PAO for their assessment-day estimate in writing, broken down by control family, before signing. The spread between quotes usually comes from differing scope assumptions rather than differing rates, and surfacing those assumptions early prevents mid-engagement change orders.

How to Budget for CMMC Certification: A Step-by-Step Approach

Start by confirming which level your contracts actually require, then commission a gap assessment to establish your baseline. Price remediation from the gap findings, not from generic benchmarks, and phase the work so quick wins land first. Reserve the C3PAO engagement early, then hold 15% to 20% contingency for the findings every project surfaces. Finally, build the ongoing annual costs into your indirect rate structure so maintenance is funded before it’s needed rather than scrambled for afterward.

CMMC Certification Cost FAQs

How much does a CMMC Level 2 audit cost?

The C3PAO assessment itself typically costs $30,000 to $100,000, depending on scope, sites, and complexity. The DoD’s own estimate for the full triennial assessment and affirmation cycle is roughly $105,000 for small entities. Preparation and remediation sit on top of that figure.

Small businesses pursuing Level 2 typically spend $50,000 to $140,000 for a first certification cycle, including gap assessment, remediation, documentation, and the C3PAO fee. Level 1 self-assessment usually costs $5,000 to $30,000.

There’s no direct reimbursement program, but compliance costs are generally allowable indirect costs and can be built into your rates. Talk to your DCAA-savvy accountant about structuring them properly.

Level 2 and Level 3 certifications last three years, so the assessment cost recurs on a triennial cycle. Annual affirmations in SPRS and ongoing maintenance costs continue every year in between.

Only where your contract allows it. Level 1 always permits self-assessment, and a subset of Level 2 contracts accept a self-assessment filed in SPRS, at a fraction of C3PAO cost. Most Level 2 work involving sensitive CUI requires third-party certification, especially from Phase 2 onward.

Most Level 2 projects take 6 to 18 months from gap assessment to certificate. Longer timelines spread costs and allow cheaper, deliberate remediation. Compressed timelines inflate consulting fees and procurement costs, and assessor scheduling backlogs make last-minute certification increasingly expensive as the November 2026 milestone approaches.

Axipro Author

Picture of Pedro Dias

Pedro Dias

Pedro has been writing online for over 10 years. With experience in all things programming, cyber security, and compliance, he is our editor-in-chief at Axipro.

Blog Highlights

Explore More Articles

For the past two years, enterprise AI risk conversations have centered on a familiar set of concerns: model bias, hallucination, data privacy, and dependency on third-party models. These are real risks, and most organizations now run some version of a governance program to manage them. But something has shifted. Organizations are no longer just deploying AI that generates content for a human to review. They’re deploying AI that acts. Agents now plan multi-step tasks, call APIs, move data between systems, execute transactions, and coordinate with other agents, often with no human checkpoint in the loop. That shift deserves more than a footnote in the existing AI risk category. It deserves its own line in the risk register: Agentic Autonomy Risk. What Is Agentic AI Risk Management? Agentic AI risk management is the practice of identifying, assessing, and controlling the risks created when AI systems take autonomous action on an organization’s behalf. Where traditional AI governance evaluates outputs (accuracy, bias, privacy), agentic AI risk management governs what agents actually do: the tools they call, the permissions they inherit, and the downstream consequences of their actions. That distinction is the reason existing risk registers struggle with agents, and it’s worth unpacking properly. What Agentic AI Actually Changes Traditional AI systems, even generative ones, are advisory. They produce an output such as a summary, a prediction, a draft email, or a classification, and a human remains the last checkpoint before anything happens in the real world. Agentic AI removes that checkpoint. An agentic system doesn’t just produce an answer. It pursues a goal. It decides which tools to call and in what order, then executes those actions directly against live systems: submitting a purchase order, modifying a database record, sending an external communication, or orchestrating a set of sub-agents to complete a broader workflow. Agentic autonomy is the degree to which a system can plan and execute actions without a human explicitly authorizing each step. It’s a spectrum rather than a binary. At one end, the AI drafts and a human approves every action. At the other, the AI operates within broad guardrails and only escalates exceptions. The further an organization moves along that spectrum, the less its exposure looks like software risk and the more it looks like delegated authority risk, the kind normally reserved for employees, contractors, and automated financial systems. Why Existing Risk Registers Miss Agentic AI Risks Most enterprise risk registers were built on a reasonably safe assumption: a human initiates consequential actions, and the technology around that human behaves deterministically. Agentic AI breaks both halves of that assumption at once. A few specific gaps show up quickly when organizations try to map agentic deployments onto existing categories. Operational risk registers assume process failures come from human error or system outages, not from a system independently choosing an unanticipated path to a stated goal. Cybersecurity risk registers are built around unauthorized external access, while an agent problem usually involves an authorized system taking unauthorized internal actions with its own legitimate credentials. Model risk frameworks, borrowed largely from financial services, evaluate output accuracy rather than action consequences, which matters most when those actions can’t be reversed. And third-party risk assessments treat vendors as static entities, not as autonomous agents that might invoke other vendors’ agents on your behalf. See our guide to the NIST AI Risk Management Framework for how output-focused frameworks are structured. The result is a governance blind spot. An organization can be compliant against its AI policy, its cybersecurity policy, and its vendor risk policy, and still have nobody accountable for the specific risk of a system initiating a harmful sequence of actions before anyone notices. Defining Agentic Autonomy Risk Agentic Autonomy Risk is the risk that an AI system, operating with delegated decision-making and execution authority, takes actions that are harmful, non-compliant, or misaligned with organizational intent before adequate human oversight can intervene. Those actions might happen independently or in coordination with other agents. It deserves standing as a named category alongside cybersecurity, operational, legal, financial, and third-party risk because the loss event itself is different. The harm is a completed action in a live system, and it may be difficult or impossible to reverse. The accountability structure is different too: when an orchestrating agent delegates to sub-agents, responsibility for the outcome gets distributed in ways existing ownership models don’t cleanly capture. So is the detection window. Traditional controls assume a human is positioned to catch an error before it compounds, but an agent can execute dozens of dependent actions faster than any human review cycle. 7 Agentic AI Risk Scenarios to Put on Your Register 1. Unauthorized autonomous decision-making. An agent takes an action within its technical permissions but outside its intended business mandate. It adjusts pricing, approves a refund, or modifies a customer record, and no policy ever explicitly authorized that scenario. 2. Goal misalignment. The agent optimizes for a literal interpretation of its objective in a way that diverges from actual business intent, particularly under ambiguous or adversarial inputs. 3. Multi-agent interactions and cascading failures. One agent’s flawed output becomes another agent’s trusted input. A single error can propagate across a chain of agents faster than anyone can detect it, amplifying the original mistake instead of containing it. 4. Excessive tool or system permissions. Agents get provisioned with broad, standing access “to be safe” rather than scoped, least-privilege access tied to specific tasks. A productivity tool quietly becomes a privilege-escalation path. 5. Regulatory non-compliance. Autonomous actions trigger obligations under data protection, financial services, employment, or sector-specific regulation, and they execute without the compliance review a human-initiated process would normally receive. 6. Explainability and accountability gaps. An autonomous action causes harm and the organization can’t clearly reconstruct why the agent chose that path, or establish whether the business owner, the AI governance function, or the vendor is accountable for the outcome. 7. Autonomous third-party actions. A vendor’s agent, integrated into your environment, takes action on your behalf, or your agent acts against a

A SOC 2 penetration test costs between $1,000 and $30,000 for most companies. A typical SaaS scope, meaning one web application, its API layer, and the cloud infrastructure behind it, usually lands between $2,000 and $20,000. Early-stage startups with a narrow scope can get an auditor-accepted test for $1,000 to $8,000, while enterprises with multiple products and hybrid infrastructure regularly spend $20,000 to $50,000 or more. The spread is wide because “penetration test” covers everything from an automated scan with a cover page to weeks of manual testing by senior engineers. Auditors know the difference, and so do the enterprise customers who asked for your SOC 2 report in the first place. This guide breaks down what drives the price, where the hidden costs sit, and how to buy a test that holds up in fieldwork without overpaying for it. What Is SOC 2 Penetration Testing?​ A SOC 2 penetration test is a simulated attack on your systems, performed by a qualified security professional, scoped to the environment covered by your SOC 2 report. The tester tries to exploit real weaknesses the way an attacker would: broken access controls, injection flaws, misconfigured cloud services, exposed credentials. The output is a report your auditor reads as evidence that your security controls work in practice, not only on paper. That last part matters. A pentest bought for SOC 2 has a second audience beyond your security team. If the report doesn’t map findings to your audit scope, document its methodology, and show remediation, it fails the job you bought it for. We cover the full deliverable in our guide to what a SOC 2-ready VAPT report includes. How Penetration Testing Fits Into SOC 2 Compliance​ SOC 2 is built on the AICPA’s Trust Services Criteria, and the Security category (the Common Criteria) applies to every report. Penetration testing is the standard way to satisfy CC7.1, which expects you to detect and monitor for new vulnerabilities, and it supports CC4.1, which covers ongoing evaluations of whether controls actually function. The AICPA’s points of focus explicitly mention vulnerability scanning and penetration testing as examples of how companies meet these criteria. In practice, the test slots into your audit timeline as an evidence item. Your auditor will ask for the report, check the test date against the audit period, and review how you handled the findings. Remediation is often scrutinized harder than the test itself, because it shows whether your vulnerability management process runs or merely exists. Is Penetration Testing Required for SOC 2?​ Strictly speaking, no. The Trust Services Criteria never use the word “mandatory” about penetration testing. You could theoretically satisfy CC7.1 with vulnerability scanning and strong monitoring alone. In reality, almost every auditor expects one, and skipping it invites two problems. First, your auditor may push back during fieldwork or add exceptions to the report. Second, the enterprise buyers reviewing your SOC 2 report increasingly look for pentest evidence specifically, and a report without it raises questions during procurement. Treat the test as effectively required and budget for it from the start of your SOC 2 compliance checklist. How Much Does SOC 2 Penetration Testing Cost? Typical Price Range for SOC 2 Pen Testing Most companies pay $1,000 to $30,000, with the median engagement for a SaaS business sitting around $12,000 to $15,000. Compliance-focused tests at the lower end of the market start around $1,000 to $5,000. Deep manual testing from established firms runs $10,000 to $30,000. Anything quoted below roughly $3,000 is almost certainly automated scanning packaged as a pentest, which auditors are getting better at spotting. Cost by Company Size (Startup, SMB, Enterprise) Company size is a proxy, not the driver. A 15-person company with three products and a legacy on-prem component will pay more than a 200-person company with one tightly scoped SaaS platform. Testers price effort, and effort follows scope. Cost by Test Type (Network, Web App, API, Cloud, Internal/External) Most SOC 2 engagements bundle two or three of these. The common package for a cloud-native SaaS company is web app plus API plus cloud configuration, which is why the $1,000 to $20,000 band comes up so often. Companies with office networks and internal systems in their audit scope add internal network testing, and the price climbs accordingly. Factors That Influence SOC 2 Penetration Testing Cost Scope and Number of Assets Tested Scope is the single biggest cost driver. Every additional application, API endpoint group, cloud account, or network segment adds testing hours. A pentest priced without a scoping call is a pentest priced on guesswork, and the guess usually favors the vendor. Complexity of Application or Infrastructure​ A simple CRUD app with two user roles tests quickly. A multi-tenant platform with role hierarchies, workflow engines, file processing, and third-party integrations takes far longer, because each of those features creates attack surface a tester has to work through manually. Authentication tiers matter especially: every distinct role needs testing for privilege escalation and cross-tenant data access. Testing Methodology (Black Box, Grey Box, White Box) Black box testing gives the tester nothing but a URL, grey box adds credentials and documentation, and white box adds source code and architecture diagrams. Grey box is the default for SOC 2 and usually the best value, since the tester spends time exploiting rather than discovering. White box costs more upfront but finds deeper issues. Black box sounds rigorous but often wastes paid hours on reconnaissance an attacker would run for free. Depth of Testing and Manual vs. Automated Approaches Automated scanning finds known vulnerability patterns. Manual testing finds business logic flaws, chained exploits, and authorization gaps that no scanner catches, and it’s the part auditors and security-literate customers actually value. The ratio of manual work to automation is the honest explanation for most price differences between two quotes covering the same scope. Tester Credentials and Firm Reputation Senior testers holding OSCP, GPEN, or CREST credentials bill higher rates, and firms with recognized methodologies charge a premium for the credibility their letterhead carries

Two compromised versions of LiteLLM sat on PyPI for roughly 40 minutes on the morning of March 24, 2026. That window was enough to capture secrets from around 434,000 CI/CD pipeline runs across nearly 2,500 organizations, including AWS, Samsung, Cisco, Salesforce, Siemens, and Deloitte. In August, researchers at CloudSEK and Hudson Rock confirmed they had obtained the raw exfiltrated data: a 153GB archive containing 433,909 files of environment variables, cloud keys, Kubernetes secrets, and API tokens harvested live from running pipelines, as covered by Help Net Security’s reporting on the credential archive. If LiteLLM runs anywhere in your stack, or you touch any AI proxy infrastructure at all, you need answers to three things: whether you were exposed, what to rotate first, and whether the rotation you did back in March actually held. That last one matters more than it sounds, because “we rotated everything” has already burned at least one very large company. How the Breach Happened The attack didn’t start with LiteLLM. On March 19, 2026, a threat group called TeamPCP compromised the build pipeline of Trivy, a vulnerability scanner half the industry runs, and pushed a poisoned release. LiteLLM’s own CI pipeline ran Trivy, so the poisoned scanner had legitimate read access to the project’s runner environment. The attackers used that to steal LiteLLM’s PyPI publishing tokens and ship two malicious releases of their own: versions 1.82.7 and 1.82.8. KICS and the Telnyx Python SDK got hit in the same campaign. The payload design is the part worth studying. The malicious package dropped a .pth startup hook into site-packages, so the code ran the moment any Python interpreter started on the machine, whether or not anything imported LiteLLM. From there it harvested environment variables, read local credential files like .aws/credentials and .kube/config, tried to move laterally across Kubernetes clusters, and installed a systemd backdoor dressed up as a generic telemetry service. InfoQ’s coverage of the PyPI compromise put downloads of the compromised release above 40,000. For scale, LiteLLM normally gets downloaded around 3 million times a day. The exfiltration had a nasty fallback, too. According to CloudSEK, stolen data was encrypted and sent to a typosquatted domain, and when that failed, the malware created a public repository inside the victim’s own GitHub account and uploaded the loot as a release asset. Some companies were publishing their own secrets to the open internet and had no idea. Worth Knowing: The malicious code only existed in the PyPI artifacts. The GitHub source repository stayed clean the whole time, so a developer reviewing the code on GitHub saw nothing wrong. Source review isn’t artifact verification. If you don’t check that what the registry serves matches the upstream source, this class of attack is invisible to you. How to Check If You Were Exposed Three checks, from quickest to most involved. 1. Confirm whether the compromised versions ever ran The malicious versions went live on PyPI at 10:39 UTC on March 24, 2026 and got quarantined about 40 minutes later. The project’s advice: treat any install from that day before 16:00 UTC as suspect. Search your lockfiles, pip caches, SBOMs, and container image histories for 1.82.7 and 1.82.8. And check your internal artifact mirrors. An Artifactory or Nexus proxy that cached the bad release in March can keep serving it internally long after PyPI pulled it. Keep the .pth mechanism in mind when you scope this. The question isn’t “which applications import LiteLLM,” it’s “which machines had the package installed at all,” because every Python process on an infected machine triggered the payload. 2. Hunt for persistence Rotation is pointless if the attacker still has a foothold. Check developer machines, CI runners, and containers for unauthorized .pth files in site-packages and for suspicious systemd units, especially anything posing as a system telemetry service. And review activity from March 24 onward, not just the 40-minute window. Persistence is there so the access outlives the infection. Pro Tip: Don’t limit the persistence hunt to live machines. Base container images rebuilt in late March may have baked the payload into every image derived from them since. Scan your image registry for the affected LiteLLM versions and for unexpected .pth files, then trace which running workloads came from flagged images. 3. Check whether your secrets are in the dump Hudson Rock has published a domain lookup tool and is running ethical disclosures for affected organizations, and CloudSEK maintains a high-confidence victim list. Use them, but know their limits. Attribution in this dataset is genuinely hard. One dump with a siriusxm.com committer email actually traced, through its self-hosted GitLab endpoints, to AdsWizz, a SiriusXM subsidiary. And a large share of the dumps are generic pipeline configurations with no identifying domain, email, or server name at all. Absence from a victim list is not evidence of absence. If your pipelines ran the compromised versions, assume exposure no matter what a lookup tool tells you. What to Rotate, in What Order The guidance from both research teams is blunt: treat every secret the LiteLLM environment could reach as compromised. That covers secrets on disk, in memory, injected into CI jobs, and anything retrievable through instance metadata services. Work down by blast radius: Priority Credential type Why it comes first 1 Cloud IAM keys (AWS, GCP, Azure) Direct control of infrastructure, data stores, and billing. This is where attackers monetize fastest. 2 GitHub and GitLab PATs, package publishing tokens These let an attacker poison your releases and turn your company into the next link in the supply chain. 3 Kubernetes service account tokens and kubeconfigs Lateral movement across clusters was built into the payload, not a theoretical risk. 4 Database passwords and third-party API keys Dumped in plain text in the archive, often with no attribution, so nobody will warn you they leaked. 5 AI provider API keys Billing abuse, quota theft, and access to whatever data flows through your LLM routing layer. One word matters more than the rest of this article: revoke, don’t just rotate. That