Which versions of pyjstat-smooth are malicious?

The following PyPI versions of pyjstat-smooth are flagged malicious: 1.5.0, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.5.5, 2.5.6, 2.5.7, 2.5.8, 2.5.9, 2.5.10, 2.5.11, 2.5.12, 2.5.13, 2.5.14, 2.5.15, 2.5.16, 2.5.17. Treat any of these as compromised.

How do I remediate pyjstat-smooth if I installed it?

pyjstat-smooth is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed pyjstat-smooth — how do I know if it already compromised me?

If pyjstat-smooth was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is pyjstat-smooth part of a known attack campaign?

Yes — pyjstat-smooth is associated with the 2026-09-pyjstat-smooth campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find pyjstat-smooth across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pyjstat-smooth (18 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pyjstat-smooth across your stack and pipelines.

Malicious package

pyjstat-smoothPyPI

pyjstat-smooth is a confirmed malicious PyPI package (MAL-2026-16267) that steals credentials and exfiltrates sensitive data (malicious versions 1.5.0, 2.5.0, 2.5.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pyjstat-smooth (PyPI)

MAL-2026-16267

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall pyjstat-smooth

What this malware does

The package hides code to exfiltrate specific files from the user's machine. The used file paths suggest it was intended to be used in a CTF-like environment.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-09-pyjstat-smooth

Reasons (based on the campaign):

files-exfiltration
obfuscation
targetted-attack
clones-real-package

Malicious versions

18 flagged

1.5.02.5.02.5.12.5.22.5.32.5.52.5.62.5.72.5.82.5.92.5.102.5.112.5.122.5.132.5.142.5.152.5.162.5.17

Indicators of compromise (SHA-256)

82a12638b869aecb566588c24c0f59c3137f9b89a26ae67222370249a7176a75

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pyjstat-smooth (18 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pyjstat-smooth across your stack and pipelines.
If you installed it — respond
pyjstat-smooth is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If pyjstat-smooth was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks pyjstat-smooth before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. pyjstat-smooth on PyPI has been identified as a malicious package (versions 1.5.0, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.5.5, 2.5.6, 2.5.7, and 10 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-09-pyjstat-smooth

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks pyjstat-smooth-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database