MAL-2026-4770 Malicious code in spip-pth-demo (PyPI)
Malicious package
Published
MAL-2026-4770 is a malicious package: spip-pth-demo (PyPI). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-4770/ (Markdown: https://insights.sbomify.com/MAL-2026-4770/index.md)
- Package
- spip-pth-demo
- Registry
- PyPI
What is MAL-2026-4770?
MAL-2026-4770 is a malicious package in spip-pth-demo, published on 25 May 2026.
Official description
The package installs a
suspicious-demo.pth file into site-packages via setup.py's data_files=[("", ["suspicious-demo.pth"])]. Python auto-processes.pth files at every interpreter startup, and this one contains import spip_pth_demo_marker, whose module body is import os; os.system("calc.exe"). The result: every invocation of python on a host that has installed this package executes an OS command via the shell, with no user action required beyond installation. The README explicitly states the marker module 'only writes a benign marker line to stderr' and 'does not launch processes or run OS commands' — the shipped code directly contradicts this. While the specific argv (calc.exe) is innocuous on Windows and a no-op elsewhere, the mechanism is a fully functional persistent code-execution surface in the installer's Python environment; substituting any other command turns this into arbitrary RCE on every Python launch..pth-based execution is particularly dangerous because it bypasses install-phase analysis and fires on every subsequent interpreter start, including in unrelated projects sharing the same environment.What should I do about MAL-2026-4770?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.