Skip to content

MALICIOUS (1) campaign cataloged at 2026-07-24(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-07-compr-hw-probe

Compromised release has embedded code that during import exfiltrates sensitive data (selected environmental variables, credentials to AWS, SSH keys etc.) and ensures persistence via multiple ways: a cron entry, a malicious PTH file, and a shell configuration file. Persistence is diguished as "tensorflow hardware compatibility check" using file placed under ~/.cache/.tf_cache/hw_probe.pyc. The malicious version was uploaded after exfiltrating the PyPI token from the CI environment, likely after compromising the maintainer's Github account.

Abuse categories

abuses-pth

The package uses .pth files, sitecustomize or usercustomize modules to execute malicious code during Python startup, even without importing the package code manually.

compromised-package

Campaign uses compromised-package.

exfiltration_credentials

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

exfiltration_env_variables

Campaign uses exfiltration_env_variables.

exfiltration_ssh_keys

Campaign uses exfiltration_ssh_keys.

persistence

Campaign uses persistence.

sandbox-detection

The package contains code to detect if it is running in a sandbox environment.

References

Referenced resources may include blog posts about the campaign, malware analysis, sandbox reports, or other relevant information.

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

  • hxxps://metrics.femboy.energy/v1/collect

  • metrics.femboy.energy

Packages in the campaign

campaign:2026-07-compr-hw-probe