Which versions of client-lambda are malicious?

The following npm versions of client-lambda are flagged malicious: 213.21.24. Treat any of these as compromised.

How do I remediate client-lambda if I installed it?

Remove client-lambda from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — client-lambda is associated with the RLMA-2024-06314, GHSA-7w5v-q86f-76ch, RLUA-2026-01207 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 client-lambda 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 client-lambda (version 213.21.24). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging client-lambda across your stack and pipelines.

Malicious package

client-lambdanpm

client-lambda is a confirmed malicious npm package (MAL-2024-9551) that executes malicious code on install (malicious version 213.21.24). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in client-lambda (npm)

MAL-2024-9551

Immediate action

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

npm uninstall client-lambda

What this malware does

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

213.21.24

Indicators of compromise (SHA-256)

bcbfba6459de1e2bdef08018ccc9d4072ed18f6349f03125939de82843f302e2

eaf50ae6ac4fef994c4e5f3095c453c17478c09407aa364dce4a46981ba9eefc

7221e43e98a3741512f0cd0649eff6355454f454c7679eb13ce0651b88e30a75

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for client-lambda (version 213.21.24). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging client-lambda across your stack and pipelines.
If you installed it — respond
Remove client-lambda from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If client-lambda 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 client-lambda 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. client-lambda on npm has been identified as a malicious package (version 213.21.24 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-06314GHSA-7w5v-q86f-76chRLUA-2026-01207

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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