Which versions of launchdarkly-ai-tooling are malicious?

The following npm versions of launchdarkly-ai-tooling are flagged malicious: 6.10.11. Treat any of these as compromised.

How do I remediate launchdarkly-ai-tooling if I installed it?

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

If launchdarkly-ai-tooling 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-ai-tooling part of a known attack campaign?

Yes — launchdarkly-ai-tooling is associated with the RLMA-2026-05139, RLUA-2026-06302 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-ai-tooling across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for launchdarkly-ai-tooling (version 6.10.11).

Malicious package

launchdarkly-ai-toolingnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

launchdarkly-ai-tooling is a confirmed malicious npm package (MAL-2026-7311) that executes malicious code on install (malicious version 6.10.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in launchdarkly-ai-tooling (npm)

MAL-2026-7311

Immediate action

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

npm uninstall launchdarkly-ai-tooling

Malicious versions

1 flagged

6.10.11

Indicators of compromise (SHA-256)

9cb4d924477a97570254754d7a4f25f8a5444390c12a7d1223b4bc24c656b9ff

342491d0a157a935b933637fc71f1abf28604b433c7c59f9afdb967cbc120683

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for launchdarkly-ai-tooling (version 6.10.11).
If you installed it — respond
Remove launchdarkly-ai-tooling 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-ai-tooling 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-ai-tooling on npm has been identified as a malicious package (version 6.10.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05139RLUA-2026-06302

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks launchdarkly-ai-tooling-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