Which versions of genosys are malicious?

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

How do I remediate genosys if I installed it?

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

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

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

Malicious package

genosysPyPI

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

MAL-2026-2818

Immediate action

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

pip uninstall genosys

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)

0f31f1dfe8053f42cee8886c1f8ae76f5da231d56ac2108e61825c79094a895e

d5166edc388937a09467f4a4e418ba9cd568bc53a58a7aa56c4598cff1b39d48

ceee291fd98b43b2ebffe4f875955759b19f43682023fee4b31fa51de4c642f5

2fb27cde30ea3d834e3160e37c203a1f8a271435cf92316a990766c5b8b9791c

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 genosys (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging genosys across your stack and pipelines.
If you installed it — respond
genosys 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 genosys 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 genosys 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. genosys 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 genosys-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