pynosist @0.1.2

Summary

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

Source: kam193 (ef7a4db1443361fe93b268c7ad8f38c5c290d5334162b57c2b534c97acbc2b5d)