Which versions of terraformness are malicious?

The following PyPI versions of terraformness are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate terraformness if I installed it?

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

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

Yes — terraformness is associated with the RLMA-2024-11178, GENERIC-standard-pypi-install-pentest, RLUA-2026-00805 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 terraformness 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 terraformness (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging terraformness across your stack and pipelines.

Malicious package

terraformnessPyPI

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

MAL-2024-11719

Immediate action

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

pip uninstall terraformness

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

c874ac9b7cb056cd788bf64bf4de4a6bf29c78f97da96fa9044d2bbebfddf81d

7e1334b85612a961d35a84191626ca90e1117b79ea5a970efb3c5a5c75875e9d

f74db70ab2e41a39e0c52a5853ee1c3ed40c189fb1d6d44197aae595f062e05d

2c2ace108f00364aa777a7b65174fb4e648aac63f141e07f1f4cf8a23e793863

116662c678c603d00003194e51918ac0d955f2e74427e0d772c5b294154b73c5

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

Campaign

RLMA-2024-11178GENERIC-standard-pypi-install-pentestRLUA-2026-00805

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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