Table of Contents

Reach SOC 2 Compliance in 6 Weeks or Less.

  /

  / How Long Does It Take to Get ISO 42001 Certified?

How Long Does It Take to Get ISO 42001 Certified?

Most organizations get ISO 42001 certified in 2 to 9 months. Companies that already hold ISO 27001 regularly land in the 2 to 5 month range, while enterprises with sprawling AI portfolios and no existing management system can take 12 months or more. The audit itself only takes days. Almost the entire calendar goes into building and operating your AI Management System (AIMS) long enough to produce evidence an auditor can actually check.

That is the short answer. The longer answer depends on your starting point, your scope, and how quickly you can get a certification body on the schedule. This article breaks down the full timeline phase by phase, the factors that stretch or compress it, and what the recertification cycle looks like once you hold the certificate.

Typical ISO 42001 Certification Timeline at a Glance

ISO/IEC 42001:2023 is the first international standard for AI management systems, published in December 2023. Because it follows the same harmonized structure as ISO 27001 and ISO 9001, the certification process will feel familiar to anyone who has been through a management system audit: build the system, run it, pass a Stage 1 and Stage 2 audit, then maintain it through annual surveillance.

Here is how timelines typically break down by company size.

Average Timeline for Small Businesses

Small companies move fastest because scope stays contained. A startup with two or three AI systems, a handful of decision makers, and short approval chains can finish scoping in a week and get policies signed off in days rather than weeks. The realistic floor for a small business starting from scratch is around 3 months. With an existing ISO 27001 program and a compliance platform already collecting evidence, 2 months is achievable.

Average Timeline for Mid-Sized Companies

Mid-sized companies usually take 6 to 9 months. The AI inventory is growing, more departments are touching AI systems, and risk assessments have to cover more use cases. Coordination becomes the hidden cost: getting engineering, legal, and product to agree on an AI policy takes longer than writing the policy itself.

Average Timeline for Enterprises

Enterprises should plan for 9 to 12 months, sometimes longer. The main drivers are AI system sprawl across business units, longer procurement cycles for certification bodies, and audits that take more days. The Stage 2 audit for a large multinational can run two weeks or more on its own, and internal alignment before the audit takes far longer than the audit itself.

Breakdown of the ISO 42001 Certification Timeline by Phase

The phases below overlap in practice. Treat the durations as effort estimates for a reasonably resourced program, not a strict sequence.

ISO 42001 Certification Timeline Phase1to5

Phase 1: Scoping and Gap Analysis (2–4 Weeks)

Everything starts with two questions: which AI systems are in scope, and how far is your current governance from what the standard requires? The gap analysis maps your existing policies and controls against the standard’s clauses and Annex A controls, and produces the project plan for everything that follows. Get the scope wrong here and every later phase inherits the mistake.

Phase 2: AIMS Design, Leadership, and AI Policy Development (2–4 Weeks)

This phase establishes the skeleton of the management system: the AI policy, governance roles, objectives, and the leadership commitments the standard requires. Executive sign-off is the gating item. The documents are not hard to write. Getting senior leadership to formally own AI governance is where programs stall.

Phase 3: AI Risk and Impact Assessments (2–6 Weeks)

ISO 42001 requires both AI risk assessments and AI impact assessments, and the distinction matters. Risk assessments look at what could go wrong for the organization. Impact assessments look at consequences for individuals and society, which is a newer discipline for most teams. This phase takes longer when you have many AI systems, high-risk use cases, or no prior methodology to adapt. The output feeds directly into your Statement of Applicability (SoA), the document that maps which Annex A controls you have selected and why.

Insider Note: Impact assessments are where auditors probe hardest, because they are the most distinctive part of ISO 42001 compared with ISO 27001. A recycled security risk register with “AI” pasted into it will get picked apart in Stage 2. Build the impact assessment methodology properly the first time.

Phase 4: Controls Implementation (2–10 Weeks)

The longest phase. Here you implement the Annex A controls selected in your SoA: AI system lifecycle documentation, data governance for training data, human oversight mechanisms, transparency measures, supplier management for third-party AI, and so on. Duration depends almost entirely on the gap analysis results. Organizations with mature engineering practices often find they already do much of this and just need to document it. Organizations without formal AI development processes are building from zero.

Phase 5: Documentation, Training, and Evidence Collection (2–8 Weeks)

Certification requires proof that the system operates, not just that it exists on paper. That means records: training completion logs, risk assessment outputs, review meeting minutes, monitoring reports. This phase runs partly in parallel with implementation, but it cannot be compressed below a certain floor because auditors want to see evidence generated over time, not a folder of documents all created the week before Stage 1.

Phase 6: Internal Audit and Management Review (2–4 Weeks)

The standard requires an internal audit of the AIMS and a formal management review before the certification audit. This is your dress rehearsal. A good internal audit surfaces nonconformities while they are still cheap to fix. Skipping or rushing it is a false economy that shows up later as Stage 2 findings.

Phase 7: Stage 1 Certification Audit (1–2 Weeks)

The certification body reviews your documentation and assesses readiness for Stage 2. The audit itself takes 1 to 3 days for most organizations. The auditor examines your scope statement, AI policy, risk and impact assessment methodology, SoA, and internal audit results, then issues findings. The 1–2 week window covers the audit plus the report.

Phase 8: Closing Nonconformities (2–4 Weeks)

Almost every Stage 1 produces findings. Minor ones can carry into Stage 2 with a corrective action plan. Major nonconformities must be closed before Stage 2 can proceed, and this is where timelines tend to slip without anyone noticing: a major finding in your risk methodology can mean redoing assessments across your whole AI inventory.

Phase 9: Stage 2 Certification Audit (1–2 Weeks)

The full audit. Auditors interview staff, sample records, and test whether the AIMS operates as documented. Expect 3 to 10 audit days depending on organization size. After Stage 2, the certification body’s independent reviewer makes the certification decision, and the certificate typically arrives 2 to 6 weeks later. The certificate is valid for three years.

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

Schedule Your Free Assessment Today

Factors That Speed Up ISO 42001 Certification

Existing ISO 27001 or ISO 9001 Certification

This is the single biggest accelerator. ISO 42001 shares the harmonized clause structure with ISO 27001 and ISO 9001, so your document control, internal audit program, management review cadence, and corrective action process carry over directly. Organizations with a mature ISO 27001 program routinely compress the timeline by 30 to 50 percent, because they are extending a working system rather than building one.

Mature AI Governance and Documentation

If you already maintain an AI inventory, run model reviews, and document training data provenance, much of the implementation phase becomes a formalization exercise. The fastest publicized certifications, completed in a matter of weeks, all involved organizations whose AI governance was substantially in place before the project started.

Dedicated Internal Resources or a Compliance Platform

A named project owner with real allocated time beats a committee every time. Compliance automation platforms help most with evidence collection and control monitoring, the mechanical work that otherwise eats weeks.

Well-Defined Scope of the AI Management System

A tight scope means fewer systems to assess, fewer controls to implement, and fewer audit days. Many organizations certify a defined product line or business unit first, then expand scope at a surveillance audit.

Early Engagement with a Certification Body

Accredited ISO 42001 auditors are still scarce. ISO/IEC 42006:2025 sets the requirements certification bodies must meet, and accreditation bodies like ANAB in the US and UKAS in the UK have only been issuing ISO 42001 accreditations since late 2024 and early 2026 respectively. Book your certification body at the start of the project, not the end. Lead times of 2 to 3 months for audit slots are common.

Pro Tip: Ask the Certification Body Two Questions

Ask the certification body two questions before signing: which accreditation body recognizes their ISO 42001 scope, and who specifically will be on your audit team. Auditor availability, not your internal readiness, is often the real critical path in the final stretch.

Factors that Slow Down ISO 42001

Factors That Slow Down ISO 42001 Certification

Broad or Undefined AIMS Scope

“All AI at the company” sounds thorough and audits terribly. Undefined scope inflates the risk assessment workload, multiplies evidence requirements, and invites Stage 1 findings about boundary ambiguity.

Limited Executive Buy-In

ISO 42001 puts explicit obligations on top management. When leadership treats the program as an IT project, policy approvals stall, resource requests queue, and the management review becomes a formality that auditors see through.

Incomplete AI System Inventory

You cannot govern what you have not cataloged. Shadow AI, meaning tools and models adopted by teams without central approval, surfaces during gap analysis and adds unplanned assessment work. Enterprises regularly discover their real AI footprint is two or three times what they assumed.

Delayed Risk and Impact Assessments

Everything downstream depends on these. Late assessments push controls implementation, which pushes evidence collection, which pushes the internal audit. A three-week slip here becomes a two-month slip at the end.

Auditor Availability and Scheduling Gaps

The pool of accredited certification bodies is growing but still small compared with ISO 27001. If you finish preparation and then start shopping for an auditor, expect to wait a quarter for a slot.

How Long Is the Gap Between Stage 1 and Stage 2 Audits?

Typically 2 weeks to 2 months. The gap exists so you can close Stage 1 findings, and its length depends on what those findings are. Organizations that sail through Stage 1 sometimes book Stage 2 within a fortnight. If Stage 1 surfaces major nonconformities, the certification body may recommend delaying Stage 2 until the fixes have generated evidence. Leaving the gap too long carries its own risk: most certification bodies expect Stage 2 within six months of Stage 1, or Stage 1 has to be repeated.

Can You Get ISO 42001 Certified in Under 3 Months?

Yes, but only under specific conditions. The organizations that have done it share a profile: existing ISO 27001 certification, a genuinely operating AI governance program before the project started, a narrow scope, and a pre-booked certification body. For them, the project is formalizing what exists, not building anything new.

For everyone else, 3 months is not realistic, and no amount of effort changes that. Auditors need evidence that your AIMS operates over time. You cannot backfill three months of monitoring records, training logs, and review minutes in three weeks, and an experienced auditor spots manufactured evidence quickly.

Timeline for ISO 42001 Recertification and Surveillance Audits

Annual Surveillance Audit Timing

Your certificate is valid for three years, but the certification body returns annually. Surveillance audits happen in years one and two after certification, typically scheduled around the anniversary of your certification date. They are shorter than the initial audit, usually 1 to 3 days, and focus on changes to your AI systems, closure of prior findings, and continued operation of core processes like risk assessment and internal audit.

Three-Year Recertification Cycle

At the end of year three, a full recertification audit renews the certificate for another three-year cycle. It resembles Stage 2 in depth but usually takes fewer days, around 60 to 70 percent of the original audit effort. Plan it 2 to 3 months before certificate expiry so any corrective actions can close before the certificate lapses. An expired certificate means starting over with a new Stage 1 and Stage 2.

How to Compress Your ISO 42001 Certification Timeline

Run Parallel Workstreams

Nothing in the standard forces you to run the phases one after another. Policy development can run alongside the AI inventory. Training can start before every control is implemented. Evidence collection should begin the day each control goes live rather than waiting until all of them do. Programs that treat the phases as strictly sequential add a month or two for no reason.

Use Compliance Automation Tools

Automation platforms cut the most time in evidence collection and continuous monitoring. Integrations that pull records automatically from your infrastructure replace the spreadsheet-and-screenshot routine that consumes analyst weeks. They also keep evidence audit-ready year-round, which pays off again at every surveillance audit.

Reuse Evidence from Existing Frameworks

Your ISO 27001 access control records, vendor assessments, and incident response documentation satisfy overlapping ISO 42001 requirements. The same applies to work done for the NIST AI Risk Management Framework or EU AI Act preparation. Map your controls across frameworks once and every subsequent audit gets cheaper. An AI impact assessment built for EU AI Act readiness covers most of what ISO 42001 asks for.

Pre-Book Your Certification Body Early

Contact certification bodies during your gap analysis, not after implementation. Booking Stage 1 three months out creates a real deadline for the internal team and removes the scheduling queue from your critical path.

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

Schedule Your Free Assessment Today

Common Mistakes That Extend the ISO 42001 Timeline

The same failure patterns show up across programs.

  • Teams write policies before completing the AI inventory, then rewrite them when shadow AI surfaces.
  • They treat the impact assessment as a copy of the security risk assessment and get sent back at Stage 1.
  • They generate all their evidence in the final month, which auditors recognize immediately.
  • They schedule the internal audit as a checkbox exercise days before Stage 1, leaving no time to fix what it finds.
  • And they wait until they feel ready before contacting a certification body, then discover the next audit slot is ten weeks away.
  • Each mistake individually costs weeks.

Together they routinely turn a six-month program into a ten-month one.

ISO 42001 certification is a 4 to 9 month project for most organizations, driven by preparation rather than the audit itself. Your starting point matters more than your ambition: existing certifications, mature AI governance, and a tight scope compress the timeline, while vague scope and late auditor booking stretch it. With most EU AI Act obligations now applying from August 2026, the organizations starting today are the ones that will have certificates in hand when customers and regulators start asking.

Frequently Asked Questions

How long does ISO 42001 certification take from scratch?

Plan for 6 to 9 months if you have no existing management system. Small companies with narrow scope can do it in 4 to 6. The long pole is operating the AIMS long enough to generate audit evidence, not writing the documentation.

Expect a 30 to 50 percent reduction. Shared clause structure means your document control, internal audit, and management review processes carry over, and controls implementation roughly halves. Most ISO 27001 certified organizations finish in 3 to 6 months.

These are personal credentials rather than organizational certification, so the timeline is short. A Lead Implementer or Lead Auditor course typically runs 4 to 5 days of training followed by an exam, so most professionals complete the credential within 2 to 4 weeks including preparation.

Controls implementation, at 6 to 12 weeks for most organizations. Close behind is evidence collection, which has a hard floor because records must accumulate over real operating time.

Three years, subject to passing annual surveillance audits in years one and two. Recertification before the three-year mark starts a new cycle.

Only with existing ISO 27001 certification, working AI governance, a narrow scope, and a certification body booked from day one. Without those, a quarter is marketing fiction. Four to six months is the honest startup answer.

Two to four weeks for most organizations. Small companies with few AI systems can finish in one week. The output is worth the time: it becomes the project plan for the entire certification effort.

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