litellm-check 0.1.0__tar.gz

litellm_check-0.1.0/LICENSE

@@ -0,0 +1,198 @@
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, in at least one of the following
+          places: within a NOTICE text file distributed as part of the
+          Derivative Works; within the Source form or documentation,
+          if provided along with the Derivative Works; or, within a
+          display generated by the Derivative Works, if and wherever
+          such third-party notices normally appear. The contents of
+          the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by you to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using the Work and assume any risks associated
+      with Your use of the Work.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any kind arising as a result
+      of any legal theory, including, but not limited to loss of profits,
+      loss of goodwill, loss of work stoppage, computer failure or malfunction,
+      or all other commercial damages or losses, even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Dylan XM
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

litellm_check-0.1.0/PKG-INFO

@@ -0,0 +1,107 @@
+Metadata-Version: 2.4
+Name: litellm-check
+Version: 0.1.0
+Summary: Self-audit CLI: scan a codebase and local Python environments for exposure to the compromised LiteLLM v1.107.0 release (PyPI, Docker Hub, GHCR) and generate an evidence report, based solely on LiteLLM's official incident announcement.
+Author: Dylan XM
+License: Apache-2.0
+Project-URL: Homepage, https://github.com/dylanXM/litellm-check
+Project-URL: Repository, https://github.com/dylanXM/litellm-check
+Project-URL: Issues, https://github.com/dylanXM/litellm-check/issues
+Project-URL: Announcement, https://docs.litellm.ai/blog/security-incident-oct-21-2026
+Keywords: litellm,supply-chain,security,scanner,incident-response,ioc
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: System Administrators
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Security
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Provides-Extra: dev
+Requires-Dist: pytest>=8.0; extra == "dev"
+Requires-Dist: ruff>=0.6; extra == "dev"
+Dynamic: license-file
+
+# litellm-check
+
+**Did the compromised LiteLLM v1.107.0 release touch your code, your images, or your Python environments?** `litellm-check` scans a source tree and/or local Python environments for the exposure surface of the 2026-10-21 LiteLLM supply-chain incident and writes an evidence report (Markdown or JSON).
+
+Every detection rule is derived from LiteLLM's **official incident announcement** — [“Contained: Oct 21, 2026 LiteLLM release v1.107.0 Compromised”](https://docs.litellm.ai/blog/security-incident-oct-21-2026) (last updated 2026-10-21 20:30 UTC). No third-party IOC lists are used. The tool collects evidence only; **it never certifies an environment as safe** — the announcement itself warns that not finding an indicator does not prove an environment is clean.
+
+Zero third-party dependencies. Python 3.11+. It reads files only and **never executes Python (or pip) inside a scanned environment** — which matters, because the announcement warns that any Python start in an affected environment re-runs the implant.
+
+## Install
+
+```bash
+pip install litellm-check        # or from a checkout:
+pip install .
+```
+
+## Usage
+
+```bash
+# Scan a project checkout
+litellm-check scan ~/src/my-service
+
+# Scan where your virtualenvs live (this is how you check installed envs)
+litellm-check scan ~/projects --format json --out report.json
+
+# CI gate: fail the job if any critical indicator is present
+litellm-check scan . --fail-on critical
+
+# Equivalent without installing
+python -m litellm_check scan <path>
+```
+
+Exit codes: `0` = scan completed (findings are reported, not gated), `1` = a finding met the `--fail-on` threshold, `2` = usage error.
+
+## What it scans
+
+| Surface | Files | What is evaluated |
+|---|---|---|
+| Dependency manifests | `requirements*.txt`, `pyproject.toml` (PEP 621 deps, optional-deps, PEP 735 dependency-groups, Poetry), `Pipfile`, `setup.py`, `setup.cfg`, conda `environment.yml` | The version spec is **evaluated**, not grepped: does it pin exactly `1.107.0` (critical), admit it — unpinned, `>=`, `~=`, Poetry `^`/`~`, wildcards (high) — or exclude it (info) |
+| Lockfiles | `poetry.lock`, `uv.lock`, `Pipfile.lock` | The resolved litellm version: `1.107.0` = critical |
+| Container definitions | `Dockerfile*`, `docker-compose*.yml` | Image tags `v1.107.0` (critical) and `latest` / `main-latest` / `main-stable` / untagged (high, they pointed at the bad image during the window); the compromised image digest anywhere in any text file (critical); GHCR digests — the announcement publishes them truncated, so those are prefix-matched and labelled as such |
+| Installed environments | any `litellm-*.dist-info` in the tree (e.g. under `.venv/`, `env/`, system site-packages you point it at) | This is the announcement's `pip show litellm` check, done by reading metadata: version `1.107.0` = critical, other versions = info |
+| Implant & marker files | anywhere in the tree | `litellm-1.107.0.dist-info`, `cook.pth`, `cook.py`, `sitecustomize.py`, `__pycache__` implant bytecode, `remote_code_loader.lock` — the exact filenames the announcement tells you to search for and delete. Critical when inside a `site-packages` directory |
+
+Rule IDs `LL-001` … `LL-013` with the incident basis and remediation for each live in [`rules/litellm.rules.json`](rules/litellm.rules.json) and are printed in full in every report.
+
+## What it does not scan / cannot prove
+
+- **A clean report is not a clean bill of health.** Environments rebuilt or deleted after exposure, images pulled without any definition file in the tree, and anything recorded only in CI logs / shell history / registry audit logs leave nothing for this tool to find.
+- “Admits” findings (LL-003, LL-007) mark **exposure surface**, not proof of installation: whether an unpinned spec actually resolved to 1.107.0 depends on whether an install ran inside the announced windows (PyPI 2026-10-21 11:39:51–13:23 UTC; Docker 11:46:56–14:20 UTC; GHCR until 13:51 UTC). Pair the scan with install timestamps.
+- It does not inspect running processes, network/egress logs, image layers, or host state outside the directory you point it at (e.g. point it at `/tmp` too if you want the daemon lock-file check to cover the real `/tmp`).
+- It does not hash installed files: the announcement publishes no wheel hashes, so no rule is built on hashes.
+- Enterprise customers on LiteLLM's private registry were **not** impacted (per the announcement); this tool checks the public artifacts only.
+
+## How to read the report
+
+- **Summary by severity** — counts first. `critical` = an artifact the vendor says to treat as compromised is present. `high` = exposure that depends on install/pull timing, or an implant-named file outside `site-packages`. `info` = litellm present but pinned/resolved/installed at a version that excludes 1.107.0 (kept in the report so reviewers can see coverage, per the announcement that all pre-1.107.0 versions are safe).
+- **Findings** — each with file:line evidence, the exact spec/tag/file matched, the incident basis (what the announcement says about it), and a remediation.
+- **Vendor response steps** — condensed from the announcement's “What to do if you are affected”: do **not** start with `pip install` (it re-executes the implant); delete the implant files from the shell; kill the daemon holding `/tmp/remote_code_loader.lock`; rebuild pinned to `litellm==1.106.2`; rotate every secret the host could reach; check CloudTrail.
+- **Detection limits** — the full statement above, printed in every report.
+
+## Demo
+
+[`examples/demo-project/`](examples/demo-project) is a deliberately exposed sample project (affected pin, floating tag, digest-pinned compose service, a fake `.venv` with inert stand-ins for the implant files). Its generated report is committed:
+
+```bash
+litellm-check scan examples/demo-project
+# 16 findings: 10 critical, 4 high, 2 info — see examples/sample-report.md
+```
+
+## Development
+
+```bash
+pip install -e ".[dev]"
+pytest -q          # 58 tests
+ruff check src tests
+```
+
+Layout mirrors the rules-as-data design: rule metadata in `rules/litellm.rules.json` (a byte-identical copy is bundled in the package; a test keeps them in sync), incident facts in `src/litellm_check/incident.py`, spec evaluation in `specs.py`, detectors in `scanner.py`.
+
+## License
+
+Apache-2.0. Not affiliated with BerriAI/LiteLLM; “LiteLLM” is used only to name the incident this tool audits.

litellm_check-0.1.0/README.md

@@ -0,0 +1,82 @@
+# litellm-check
+
+**Did the compromised LiteLLM v1.107.0 release touch your code, your images, or your Python environments?** `litellm-check` scans a source tree and/or local Python environments for the exposure surface of the 2026-10-21 LiteLLM supply-chain incident and writes an evidence report (Markdown or JSON).
+
+Every detection rule is derived from LiteLLM's **official incident announcement** — [“Contained: Oct 21, 2026 LiteLLM release v1.107.0 Compromised”](https://docs.litellm.ai/blog/security-incident-oct-21-2026) (last updated 2026-10-21 20:30 UTC). No third-party IOC lists are used. The tool collects evidence only; **it never certifies an environment as safe** — the announcement itself warns that not finding an indicator does not prove an environment is clean.
+
+Zero third-party dependencies. Python 3.11+. It reads files only and **never executes Python (or pip) inside a scanned environment** — which matters, because the announcement warns that any Python start in an affected environment re-runs the implant.
+
+## Install
+
+```bash
+pip install litellm-check        # or from a checkout:
+pip install .
+```
+
+## Usage
+
+```bash
+# Scan a project checkout
+litellm-check scan ~/src/my-service
+
+# Scan where your virtualenvs live (this is how you check installed envs)
+litellm-check scan ~/projects --format json --out report.json
+
+# CI gate: fail the job if any critical indicator is present
+litellm-check scan . --fail-on critical
+
+# Equivalent without installing
+python -m litellm_check scan <path>
+```
+
+Exit codes: `0` = scan completed (findings are reported, not gated), `1` = a finding met the `--fail-on` threshold, `2` = usage error.
+
+## What it scans
+
+| Surface | Files | What is evaluated |
+|---|---|---|
+| Dependency manifests | `requirements*.txt`, `pyproject.toml` (PEP 621 deps, optional-deps, PEP 735 dependency-groups, Poetry), `Pipfile`, `setup.py`, `setup.cfg`, conda `environment.yml` | The version spec is **evaluated**, not grepped: does it pin exactly `1.107.0` (critical), admit it — unpinned, `>=`, `~=`, Poetry `^`/`~`, wildcards (high) — or exclude it (info) |
+| Lockfiles | `poetry.lock`, `uv.lock`, `Pipfile.lock` | The resolved litellm version: `1.107.0` = critical |
+| Container definitions | `Dockerfile*`, `docker-compose*.yml` | Image tags `v1.107.0` (critical) and `latest` / `main-latest` / `main-stable` / untagged (high, they pointed at the bad image during the window); the compromised image digest anywhere in any text file (critical); GHCR digests — the announcement publishes them truncated, so those are prefix-matched and labelled as such |
+| Installed environments | any `litellm-*.dist-info` in the tree (e.g. under `.venv/`, `env/`, system site-packages you point it at) | This is the announcement's `pip show litellm` check, done by reading metadata: version `1.107.0` = critical, other versions = info |
+| Implant & marker files | anywhere in the tree | `litellm-1.107.0.dist-info`, `cook.pth`, `cook.py`, `sitecustomize.py`, `__pycache__` implant bytecode, `remote_code_loader.lock` — the exact filenames the announcement tells you to search for and delete. Critical when inside a `site-packages` directory |
+
+Rule IDs `LL-001` … `LL-013` with the incident basis and remediation for each live in [`rules/litellm.rules.json`](rules/litellm.rules.json) and are printed in full in every report.
+
+## What it does not scan / cannot prove
+
+- **A clean report is not a clean bill of health.** Environments rebuilt or deleted after exposure, images pulled without any definition file in the tree, and anything recorded only in CI logs / shell history / registry audit logs leave nothing for this tool to find.
+- “Admits” findings (LL-003, LL-007) mark **exposure surface**, not proof of installation: whether an unpinned spec actually resolved to 1.107.0 depends on whether an install ran inside the announced windows (PyPI 2026-10-21 11:39:51–13:23 UTC; Docker 11:46:56–14:20 UTC; GHCR until 13:51 UTC). Pair the scan with install timestamps.
+- It does not inspect running processes, network/egress logs, image layers, or host state outside the directory you point it at (e.g. point it at `/tmp` too if you want the daemon lock-file check to cover the real `/tmp`).
+- It does not hash installed files: the announcement publishes no wheel hashes, so no rule is built on hashes.
+- Enterprise customers on LiteLLM's private registry were **not** impacted (per the announcement); this tool checks the public artifacts only.
+
+## How to read the report
+
+- **Summary by severity** — counts first. `critical` = an artifact the vendor says to treat as compromised is present. `high` = exposure that depends on install/pull timing, or an implant-named file outside `site-packages`. `info` = litellm present but pinned/resolved/installed at a version that excludes 1.107.0 (kept in the report so reviewers can see coverage, per the announcement that all pre-1.107.0 versions are safe).
+- **Findings** — each with file:line evidence, the exact spec/tag/file matched, the incident basis (what the announcement says about it), and a remediation.
+- **Vendor response steps** — condensed from the announcement's “What to do if you are affected”: do **not** start with `pip install` (it re-executes the implant); delete the implant files from the shell; kill the daemon holding `/tmp/remote_code_loader.lock`; rebuild pinned to `litellm==1.106.2`; rotate every secret the host could reach; check CloudTrail.
+- **Detection limits** — the full statement above, printed in every report.
+
+## Demo
+
+[`examples/demo-project/`](examples/demo-project) is a deliberately exposed sample project (affected pin, floating tag, digest-pinned compose service, a fake `.venv` with inert stand-ins for the implant files). Its generated report is committed:
+
+```bash
+litellm-check scan examples/demo-project
+# 16 findings: 10 critical, 4 high, 2 info — see examples/sample-report.md
+```
+
+## Development
+
+```bash
+pip install -e ".[dev]"
+pytest -q          # 58 tests
+ruff check src tests
+```
+
+Layout mirrors the rules-as-data design: rule metadata in `rules/litellm.rules.json` (a byte-identical copy is bundled in the package; a test keeps them in sync), incident facts in `src/litellm_check/incident.py`, spec evaluation in `specs.py`, detectors in `scanner.py`.
+
+## License
+
+Apache-2.0. Not affiliated with BerriAI/LiteLLM; “LiteLLM” is used only to name the incident this tool audits.

litellm_check-0.1.0/pyproject.toml

@@ -0,0 +1,52 @@
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "litellm-check"
+version = "0.1.0"
+description = "Self-audit CLI: scan a codebase and local Python environments for exposure to the compromised LiteLLM v1.107.0 release (PyPI, Docker Hub, GHCR) and generate an evidence report, based solely on LiteLLM's official incident announcement."
+readme = "README.md"
+requires-python = ">=3.11"
+license = { text = "Apache-2.0" }
+authors = [
+    { name = "Dylan XM" },
+]
+keywords = ["litellm", "supply-chain", "security", "scanner", "incident-response", "ioc"]
+classifiers = [
+    "Development Status :: 3 - Alpha",
+    "Intended Audience :: Developers",
+    "Intended Audience :: System Administrators",
+    "License :: OSI Approved :: Apache Software License",
+    "Programming Language :: Python :: 3",
+    "Topic :: Security",
+]
+dependencies = []
+
+[project.urls]
+Homepage = "https://github.com/dylanXM/litellm-check"
+Repository = "https://github.com/dylanXM/litellm-check"
+Issues = "https://github.com/dylanXM/litellm-check/issues"
+Announcement = "https://docs.litellm.ai/blog/security-incident-oct-21-2026"
+
+[project.optional-dependencies]
+dev = [
+    "pytest>=8.0",
+    "ruff>=0.6",
+]
+
+[project.scripts]
+litellm-check = "litellm_check.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+litellm_check = ["rules/*.json"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+
+[tool.ruff]
+# fixtures are intentionally dirty sample projects, not real code
+extend-exclude = ["tests/fixtures", "examples"]

litellm_check-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

litellm_check-0.1.0/src/litellm_check/__init__.py

@@ -0,0 +1,14 @@
+"""LiteLLM Check - exposure self-audit for the compromised v1.107.0 release.
+
+Scans a source tree and/or local Python environments for the exposure
+surface of the 2026-10-21 LiteLLM supply-chain incident: dependency
+specs and lockfiles that pin or admit litellm==1.107.0, container image
+tags/digests named in the incident announcement, installed-distribution
+metadata, and the implant/marker files the announcement lists.
+
+Every detection rule is derived from LiteLLM's official incident
+announcement. The tool collects evidence only; it never certifies an
+environment as safe.
+"""
+
+__version__ = "0.1.0"

litellm_check-0.1.0/src/litellm_check/__main__.py

@@ -0,0 +1,4 @@
+from .cli import main
+
+if __name__ == "__main__":
+    raise SystemExit(main())

litellm_check-0.1.0/src/litellm_check/cli.py

@@ -0,0 +1,93 @@
+"""Command line interface: `litellm-check scan <path>`."""
+
+from __future__ import annotations
+
+import argparse
+import sys
+from pathlib import Path
+
+from . import __version__
+from .report import render_json, render_markdown
+from .rules import load_rules
+from .scanner import SEVERITY_ORDER, scan_path
+
+FAIL_LEVELS = ["critical", "high", "medium", "low", "info"]
+
+
+def _build_parser() -> argparse.ArgumentParser:
+    parser = argparse.ArgumentParser(
+        prog="litellm-check",
+        description=(
+            "Scan a source tree and/or local Python environments for "
+            "exposure to the compromised LiteLLM v1.107.0 release "
+            "(PyPI / Docker Hub / GHCR, 2026-10-21) and produce an "
+            "evidence report. Rules derive solely from LiteLLM's "
+            "official incident announcement."
+        ),
+    )
+    parser.add_argument("--version", action="version",
+                        version=f"%(prog)s {__version__}")
+    sub = parser.add_subparsers(dest="command", required=True)
+
+    scan = sub.add_parser("scan", help="Scan a directory and report findings.")
+    scan.add_argument("path", help="Directory to scan.")
+    scan.add_argument(
+        "--format", choices=["md", "json"], default="md",
+        help="Report format (default: md).",
+    )
+    scan.add_argument(
+        "--out", default=None,
+        help="Write the report to this file instead of stdout.",
+    )
+    scan.add_argument(
+        "--fail-on", choices=FAIL_LEVELS + ["none"], default="none",
+        help=(
+            "Exit with code 1 when any finding is at or above this "
+            "severity (for CI). Default: none (always exit 0)."
+        ),
+    )
+    scan.add_argument(
+        "--rules", default=None,
+        help="Path to an alternate rules JSON file.",
+    )
+    return parser
+
+
+def main(argv: list[str] | None = None) -> int:
+    args = _build_parser().parse_args(argv)
+
+    if args.command == "scan":
+        target = Path(args.path)
+        if not target.is_dir():
+            print(f"error: {target} is not a directory", file=sys.stderr)
+            return 2
+        ruleset = load_rules(args.rules)
+        result = scan_path(target, ruleset)
+        text = (
+            render_json(result, ruleset)
+            if args.format == "json"
+            else render_markdown(result, ruleset)
+        )
+        if args.out:
+            Path(args.out).write_text(text, encoding="utf-8")
+            print(
+                f"litellm-check: {len(result.findings)} finding(s) in "
+                f"{result.files_scanned} file(s); report written to {args.out}",
+                file=sys.stderr,
+            )
+        else:
+            sys.stdout.write(text)
+        if args.fail_on != "none":
+            threshold = SEVERITY_ORDER[args.fail_on]
+            worst = min(
+                (SEVERITY_ORDER.get(f.severity, 99) for f in result.findings),
+                default=99,
+            )
+            if worst <= threshold:
+                return 1
+        return 0
+    return 2
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

litellm_check-0.1.0/src/litellm_check/incident.py

@@ -0,0 +1,78 @@
+"""Incident facts, transcribed from LiteLLM's official announcement.
+
+Source: "Contained: Oct 21, 2026 LiteLLM release v1.107.0 Compromised"
+https://docs.litellm.ai/blog/security-incident-oct-21-2026
+(last updated 2026-10-21 20:30 UTC; read 2026-10-22).
+
+Only facts stated in that announcement live here. Third-party write-ups
+mention additional indicators (file hashes, extra marker files, C2
+endpoints); they are deliberately NOT used, because the announcement -
+the vendor's own account - is the sole basis for this tool's rules.
+"""
+
+from __future__ import annotations
+
+SOURCE_URL = "https://docs.litellm.ai/blog/security-incident-oct-21-2026"
+SOURCE_TITLE = "LiteLLM incident announcement: Oct 21, 2026 LiteLLM release v1.107.0 Compromised"
+SOURCE_UPDATED = "2026-10-21 20:30 UTC"
+
+PACKAGE = "litellm"
+AFFECTED_VERSION = "1.107.0"
+AFFECTED_VERSION_TUPLE = (1, 107, 0)
+# "For the time being, please pin your version to 1.106.2 or any explicit
+# version published prior to now." / "All previous versions are safe."
+RECOMMENDED_PIN = "1.106.2"
+
+# Exposure windows (UTC, 2026-10-21), per the announcement.
+PYPI_WINDOW = "2026-10-21 11:39:51-13:23 UTC"
+DOCKER_WINDOW = "2026-10-21 11:46:56-14:20 UTC"
+GHCR_WINDOW = "2026-10-21 11:46:56-13:51 UTC"
+
+# Compromised image index (Docker Hub tags v1.107.0, latest, main-latest,
+# main-stable pointed at it). The announcement gives this digest in full.
+COMPROMISED_DIGEST = (
+    "sha256:1bbcb1443bc962e45f5aad53fe3d2c30600e0379715fb6c664cdd3ac126c339e"
+)
+
+# GHCR repositories named in the announcement. The announcement publishes
+# their digests TRUNCATED (shown with an ellipsis); only the prefix is
+# recorded here and prefix matching is labelled as such in findings.
+GHCR_REPOS = {
+    "ghcr.io/berriai/litellm": "sha256:1bbcb1443bc9",
+    "ghcr.io/berriai/litellm-database": "sha256:c00f9d92c427",
+    "ghcr.io/berriai/litellm-non_root": "sha256:7b00e91cd2fe",
+}
+
+# Image repositories in scope: the announcement names the GHCR paths
+# explicitly and lists the same tags for Docker Hub, whose repository is
+# berriai/litellm (and the -database / -non_root variants).
+IMAGE_REPOS = {
+    "berriai/litellm",
+    "berriai/litellm-database",
+    "berriai/litellm-non_root",
+    *GHCR_REPOS.keys(),
+}
+
+AFFECTED_TAG = "v1.107.0"
+FLOATING_TAGS = {"latest", "main-latest", "main-stable"}
+
+# Filesystem evidence named in the announcement.
+# - "Search filesystem evidence for litellm-1.107.0.dist-info, cook.pth,
+#    and sitecustomize.py."
+# - Response step 1 adds cook.py and __pycache__/cook*.pyc /
+#   sitecustomize*.pyc.
+# - Response step 2: the detached daemon holds /tmp/remote_code_loader.lock;
+#   step 4: "If the marker file exists, the exfil is confirmed."
+IMPLANT_FILES_EXACT = {"cook.pth", "cook.py"}
+SITECUSTOMIZE_FILE = "sitecustomize.py"
+DAEMON_MARKER_FILE = "remote_code_loader.lock"
+
+# The announcement's own response steps, condensed for the report.
+RESPONSE_STEPS = [
+    "Do NOT start with pip install: any Python start in an affected environment runs cook.pth and sitecustomize.py again, and that includes running pip.",
+    "From the shell, delete cook.pth, cook.py, sitecustomize.py and any matching __pycache__/cook*.pyc and sitecustomize*.pyc from every affected site-packages.",
+    "Kill the detached python daemon (it holds /tmp/remote_code_loader.lock).",
+    "Reinstall pinned to litellm==1.106.2. Rebuilding images and venvs from scratch is better.",
+    "If 1.107.0 was ever installed on a host with outbound internet, assume the exfiltration succeeded; rotate everything the host could reach: the instance/task IAM role, every provider key stored in the LiteLLM proxy DB plus the master and virtual keys, the DATABASE_URL password, and any secret in the environment of any process on the host.",
+    "Check CloudTrail for GetCallerIdentity from the instance role around install time, then for use of the role's credentials from outside your infrastructure.",
+]