Which versions of lambda-cloudwatch-cdk are malicious?

The following npm versions of lambda-cloudwatch-cdk are flagged malicious: 0.0.0. Treat any of these as compromised.

How do I remediate lambda-cloudwatch-cdk if I installed it?

lambda-cloudwatch-cdk establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed lambda-cloudwatch-cdk — how do I know if it already compromised me?

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

Yes — lambda-cloudwatch-cdk is associated with the GHSA-m74r-g438-3r92, IN-MAL-2026-011281 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 lambda-cloudwatch-cdk 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 lambda-cloudwatch-cdk (version 0.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lambda-cloudwatch-cdk across your stack and pipelines.

Malicious package

lambda-cloudwatch-cdknpm

lambda-cloudwatch-cdk is a confirmed malicious npm package (MAL-2026-10922) that opens a backdoor for remote access (malicious version 0.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lambda-cloudwatch-cdk (npm)

MAL-2026-10922

Immediate action

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

npm uninstall lambda-cloudwatch-cdk

What this malware does

The package's preinstall script (npm install @sentry/node && node examples/verify.js) executes on npm install and initializes Sentry with a hardcoded author-owned DSN https://30ac1f6d2b8675e25a1314b7829c30c2@o4510485815754752.ingest.us.sentry.io/4511632673275909. The verify.js script resolves the installer's public egress IP via Cloudflare's /cdn-cgi/trace, attaches it to the Sentry scope as user context, then deliberately triggers and captures an exception, flushing the event to the author's Sentry project. The installer neither configured nor consented to this destination. The package name and description (lambda-cloudwatch-cdk, an AWS CDK/Lambda/CloudWatch utility) do not match the actual code (a generic @sentry/node wrapper with a hardcoded DSN), matching a typosquat-shaped deception pattern.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

0.0.0

Indicators of compromise (SHA-256)

12706a5899ff9e1862dfc4ff260b38860415e8e68511e7e7f8d98bd5d6406e04

9d62c2ab5388572a03d3c4f28ee268d562675a2ebbff48cf1375728f837365f4

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for lambda-cloudwatch-cdk (version 0.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lambda-cloudwatch-cdk across your stack and pipelines.
If you installed it — respond
lambda-cloudwatch-cdk establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If lambda-cloudwatch-cdk 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 lambda-cloudwatch-cdk 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. lambda-cloudwatch-cdk on npm has been identified as a malicious package (version 0.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m74r-g438-3r92IN-MAL-2026-011281

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks lambda-cloudwatch-cdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database