Which versions of cdk-insights are malicious?

The following npm versions of cdk-insights are flagged malicious: 1.41.2, 1.42.3. Treat any of these as compromised.

How do I remediate cdk-insights if I installed it?

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

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

Yes — cdk-insights is associated with the IN-MAL-2026-004226, IN-MAL-2026-005797 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 cdk-insights 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 cdk-insights (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cdk-insights across your stack and pipelines.

Malicious package

cdk-insightsnpm

cdk-insights is a confirmed malicious npm package (MAL-2026-4508) that steals credentials and exfiltrates sensitive data (malicious versions 1.41.2, 1.42.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cdk-insights (npm)

MAL-2026-4508

Immediate action

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

npm uninstall cdk-insights

What this malware does

The package contains code in dist/entry.js and dist/index.js that invokes npm publish programmatically combined with writeFileSync operations — the canonical wormable auto-publication pattern (enumerate maintainer's other packages, rewrite their package.json, republish under the installer's npm credentials). Additionally, dist/aspects/CdkInsightsAspect.js, dist/entry.js, and dist/index.js contain multiple HTTP POST sinks consistent with hardcoded C2 / data-exfiltration endpoints, and CdkInsightsAspect.js contains ping-based network reconnaissance. The combination of wormable self-propagation infrastructure plus exfiltration POST endpoints in install/import-reachable code is unambiguous supply-chain attack shape: any developer or CI system installing this package risks (a) having installer-side data POSTed to attacker-controlled endpoints and (b) having their npm credentials abused to republish malicious versions of their other packages.

Malicious versions

2 flagged

1.41.21.42.3

Indicators of compromise (SHA-256)

fa41acb776dbedfe93c37899783a5e54b78017ac31576c798a27eae6b9e9ec89

c881a135de8104d4fb3610e23f98105d97692a8c20b0cad8fb4a45c3d2052e46

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

Campaign

IN-MAL-2026-004226IN-MAL-2026-005797

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cdk-insights-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

Explore

All malware advisories How O3 detects malware Vulnerability database