Which versions of launchdarkly-cpp-internal are malicious?

The following npm versions of launchdarkly-cpp-internal are flagged malicious: 0.13.0, 9.9.9. Treat any of these as compromised.

How do I remediate launchdarkly-cpp-internal if I installed it?

Remove launchdarkly-cpp-internal 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 launchdarkly-cpp-internal — how do I know if it already compromised me?

If launchdarkly-cpp-internal was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is launchdarkly-cpp-internal part of a known attack campaign?

Yes — launchdarkly-cpp-internal is associated with the RLMA-2024-01276, RLUA-2024-06816, RLUA-2025-06395 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 launchdarkly-cpp-internal across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for launchdarkly-cpp-internal (2 malicious versions).

Malicious package

launchdarkly-cpp-internalnpm

Advisory published Jun 25, 2024Updated Dec 24, 2025

launchdarkly-cpp-internal is a confirmed malicious npm package (MAL-2024-2595) that executes malicious code on install (malicious versions 0.13.0, 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in launchdarkly-cpp-internal (npm)

MAL-2024-2595

Immediate action

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

npm uninstall launchdarkly-cpp-internal

Malicious versions

2 flagged

0.13.09.9.9

Indicators of compromise (SHA-256)

6aee0610fdd2d07b25271f6fb10743921e705d65cbaf590e0da2f678f62f4874

04de0d9362e1c2fb237453f1b9b4ea79064095c579817676eb24137dcffa5d30

5ae8638c93a49bcaa3e8d2d73a836182c0dc9cd06194c88df87c508eb7ef42fe

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for launchdarkly-cpp-internal (2 malicious versions).
If you installed it — respond
Remove launchdarkly-cpp-internal 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 launchdarkly-cpp-internal was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. launchdarkly-cpp-internal on npm has been identified as a malicious package (versions 0.13.0, 9.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-01276RLUA-2024-06816RLUA-2025-06395

Credits

ReversingLabs · finder

Detect & block this

O3 blocks launchdarkly-cpp-internal-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