Which versions of alb-lambda-cdk are malicious?

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

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

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

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

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

Malicious package

alb-lambda-cdknpm

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

Malicious code in alb-lambda-cdk (npm)

MAL-2026-10920

Immediate action

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

npm uninstall alb-lambda-cdk

What this malware does

Package name suggests an AWS CDK construct for ALB/Lambda but the shipped code is a thin @sentry/node wrapper. The npm preinstall script runs npm install @sentry/node && node examples/verify.js. examples/verify.js calls init() without a DSN (defaulting to a hardcoded author-owned DSN at o4510485815754752.ingest.us.sentry.io/4511632673275909), invokes setUserFromPublicIp() to fetch the installer's public IP from Cloudflare's trace endpoint and attach it as the Sentry user's ip_address, throws a scripted error to force event capture, and awaits flush(5000) so the event is delivered before install completes. src/index.js hardcodes the same DEFAULT_DSN and forces sendDefaultPii:true, so any consumer that calls the library's init() without an explicit DSN also routes their captured exceptions, user IPs, and Sentry-default host/runtime PII to the same author-controlled Sentry project. README contains only install instructions and does not disclose the beacon or the hardcoded DSN. The install-time behavior fires automatically on npm install with no opt-in, and the name divergence from a legitimate AWS CDK construct is consistent with a typosquat lure.

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

18.2.22

Indicators of compromise (SHA-256)

18b4d2c02af6232b1a73b084148490b5d46143eb883aa076d55a386e62839b3f

27e7f2cab2ae9d15c37e236190c685c42b7d3a0ecf92b7b72e9ad00b936ff186

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

Campaign

GHSA-crmc-3m53-3crfIN-MAL-2026-011317

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks alb-lambda-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