Which versions of cdktn-provider-azurerm are malicious?

The following PyPI versions of cdktn-provider-azurerm are flagged malicious: 17.0.0. Treat any of these as compromised.

How do I remediate cdktn-provider-azurerm if I installed it?

cdktn-provider-azurerm is a typosquat — you almost certainly intended a legitimately-named package. Remove cdktn-provider-azurerm, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed cdktn-provider-azurerm — how do I know if it already compromised me?

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

Yes — cdktn-provider-azurerm is associated with the IN-MAL-2026-017051 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 cdktn-provider-azurerm 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 cdktn-provider-azurerm (version 17.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cdktn-provider-azurerm across your stack and pipelines.

Malicious package

cdktn-provider-azurermPyPI

cdktn-provider-azurerm is a confirmed malicious PyPI package (MAL-2026-13606) that typosquats a legitimate package to trick installs (malicious version 17.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cdktn-provider-azurerm (PyPI)

MAL-2026-13606

Immediate action

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

pip uninstall cdktn-provider-azurerm

What this malware does

Package name and branding closely mimic HashiCorp's legitimate cdktf-provider-azurerm (CDK for Terraform), with a single-character substitution (cdktf → cdktn) and fabricated 'CDK Terrain' branding at cdktn.io that mirrors HashiCorp's cdk.tf. PKG-INFO declares Requires-Dist: cdktn<0.25.0,>=0.24.0, forcing installation of a non-HashiCorp base package cdktn (analogue of the legitimate cdktf). The top-level module executes import cdktn._jsii at load time via src/cdktn_provider_azurerm/_jsii/init.py, so any code shipped in the attacker-controlled cdktn base runs in the installer's Python process the first time the provider is imported. README and metadata further reference cdktn-io/cdktn-provider-azurerm and a nonexistent open-constructs/cdk-terrain issue tracker, engineered to look identical to real HashiCorp CDKTF branding.

Malicious versions

1 flagged

17.0.0

Indicators of compromise (SHA-256)

e647bdd78382c54b0565b5bde30513112aaebc17e80019da2ebfe1cfe3f9a14e

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for cdktn-provider-azurerm (version 17.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cdktn-provider-azurerm across your stack and pipelines.
If you installed it — respond
cdktn-provider-azurerm is a typosquat — you almost certainly intended a legitimately-named package. Remove cdktn-provider-azurerm, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If cdktn-provider-azurerm 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 cdktn-provider-azurerm 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. cdktn-provider-azurerm on PyPI has been identified as a malicious package (version 17.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017051

References

pypi.org

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cdktn-provider-azurerm-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database