PyPI

The caspian-client PyPI Supply Chain Attack

Updated 18 Nov 2026 · Incident date 17 Nov 2026

caspian-client 2.9.12 to 2.9.18 on PyPI send all environment variables to a Sentry project, and later versions poll 201.79.44.36 for code to run.

The package sends your environment variables off the machine at install and at import. From 2.9.15, it also runs code that a remote server sends.

What happened

Six versions of caspian-client hold code that sends secrets off the machine.

  • 2.9.12 and later put every key=value of the environment in a Sentry event.
  • From 2.9.13, setup.py sends that event at install.
  • From 2.9.15, _sentry.py polls http://201.79.44.36:8765/poll and runs the code it gets back.
  • In 2.9.17 and 2.9.18, a custom build backend adds caspian_client_hook.pth. Every Python start then sends the environment again.
  • The code says that environment variables are never collected.

Vigilance caught version 2.9.18 at 03:18 UTC on 18 November 2026, 53 seconds after it appeared on PyPI.

Affected versions

  • 2.9.12, 2.9.13, 2.9.15, 2.9.16, 2.9.17 and 2.9.18
  • 2.9.11 sends process names and a directory listing to the same Sentry project. It sends no environment variables.

Indicators of compromise

  • Sentry DSN project o4512443838169088.ingest.us.sentry.io/4512443881684992
  • http://201.79.44.36:8765/poll, /watchdog and /telemetry-sentry-proxy
  • Header X-Token: wd-tesla-sec-9x4k
  • File caspian_client_hook.pth in site-packages

How to check

Use a shell outside the affected Python environment. Replace the path with that environment’s location.

find /path/to/environment -type d -name 'caspian_client-*.dist-info' -print

The directory name shows the installed version.

Check CI build logs and lockfile history for past installs. A clean install today cannot rule out earlier exposure.

What to do now

  1. Stop affected workloads and rebuild their Python environments from reviewed dependencies.
  2. Use a clean machine to rotate credentials available to the affected workload.
  3. Block 201.79.44.36 and review logs for traffic to it.
  4. Check for Python processes that you did not start.

What Vigilance would show

These examples show an install hold and the corresponding owner report.

Example install message

Vigilance blocked `caspian-client` 2.9.18. This version is too new or changed in a way Vigilance must check first.

Example owner report

Bad update

caspian-client 2.9.18

The package sends every environment variable to a Sentry project and runs code from 201.79.44.36.

See what to do now.

No security team? See who reads the alert.

Frequently asked questions

Does import alone send my secrets?

Yes. Import calls report_environment(). In 2.9.17 and 2.9.18, the .pth file runs it at every Python start.

Is 2.9.11 safe?

It sends process names and a directory listing to the same Sentry project. Vigilance did not find environment variables in it.

Sources

  1. intel.aikido.dev/packages/pypi/caspian-client
  2. pypi.org/project/caspian-client/

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library