Skip to content

MALICIOUS (1) campaign cataloged at 2026-04-16(2).

  1. The campaign has clearly malicious intent, like infostealers.
  2. This is just the date of creating the catalog entry. It may not reflect the date of creation of the campaign itself.

2026-04-genosys

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.

Abuse categories

exfiltration_credentials

The package attempts to steal credentials, like passwords or API keys.

files_exfiltration

Campaign uses files_exfiltration.

obfuscation

Code uses obfuscation techniques to hide its true purpose.

peristence_autorun

Campaign uses peristence_autorun.

persistence

Campaign uses persistence.

through_dependency

The malicious code is intentionally included in a dependency of the package

URLs with payloads, characteristic domains, C&C IPs, repositories with malicious code, etc.

  • hxxps://161.97.81.147:8080

  • 161.97.81.147

Packages in the campaign

campaign:2026-04-genosys