Which versions of pynosist are malicious?

The following PyPI versions of pynosist are flagged malicious: 0.1.0, 0.1.1, 0.1.2. Treat any of these as compromised.

How do I remediate pynosist if I installed it?

pynosist 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 pynosist — how do I know if it already compromised me?

If pynosist 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 pynosist part of a known attack campaign?

Yes — pynosist is associated with the 2026-04-genosys 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 pynosist 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 pynosist (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pynosist across your stack and pipelines.

Malicious package

pynosistPyPI

Malicious code in pynosist (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2819

Immediate action

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

pip uninstall pynosist

What this malware does

The campaign is built from a benign-like package (e.g. genosys) and the malicious dependency (e.g. pynosist). The dependency uses a PTH file to trigger malicious action upon Python start. First, it ensures persistency e.g., through the autostart registry key. Then, based on the encrypted config, an exfiltration demon is started. It registeres the instance in the C2 server and starts searching the file system looking for files matching given filename patterns and then monitoring changes. Discovered files are exfiltrated to hardcoded remote target. In pynosist, the embeded configuration looks for *pemasukan*,*pengeluaran* and during analysis further updates from C2 changed patterns to "*privatekey*", "*privatekeys*", "*phrase*", "*private_key*", "*private-key*", "*airdrop*", "*private_keys*". The communication with C2 is secured by an embedded certificate.

The PyPI packages are used as dependencies in newly-created crypto-related repositories on GitHub.

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

Campaign: 2026-04-genosys

Reasons (based on the campaign):

files-exfiltration
peristence-autorun
obfuscation
The malicious code is intentionally included in a dependency of the package
exfiltration-credentials
persistence
crypto-related

Malicious versions

3 flagged

0.1.00.1.10.1.2

Indicators of compromise (SHA-256)

22099e06b775b693ee968f0c24992f9b3e4a07c5111dca77b8eacb80fa848570

e04256eb1c50315d6a1880695d0f2dad1cbe76ab0d7d85a300d78081bbe87ceb

faa7a26abfc86abcff2d4f0dc03bc01e874812c755e498ba8c5de57cb97049ba

ef7a4db1443361fe93b268c7ad8f38c5c290d5334162b57c2b534c97acbc2b5d

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 pynosist (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pynosist across your stack and pipelines.
If you installed it — respond
pynosist 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 pynosist 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 pynosist 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. pynosist on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-04-genosys

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks pynosist-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