Malware in @servicetitan/launchdarkly-service
Malware was discovered in the npm package @servicetitan/launchdarkly-service. Any computer with this package installed or running should be considered fully compromised, requiring immediate rotation of all secrets and keys from a separate system.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @servicetitan/launchdarkly-service
A malicious version of the npm package @servicetitan/launchdarkly-service was published and made available to users. The package contained malware that could grant full control of an affected system to an outside entity.\n\nAny computer that installed or ran this package should be considered fully compromised. All secrets, keys, and credentials stored on affected systems must be rotated immediately from a different, uncompromised computer.\n\nWhile the malicious package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise. A full security audit and potential system rebuild may be necessary for affected systems.
Indicators of compromise
- Packages
- @servicetitan/launchdarkly-service
Remediation
- Immediately remove the @servicetitan/launchdarkly-service package from all systems
- Rotate all secrets, keys, and credentials from a separate, uncompromised computer
- Conduct a full security audit of any system that had this package installed
- Consider rebuilding affected systems from clean media
- Monitor affected systems for signs of persistent compromise or lateral movement
- Review access logs and network traffic from the period when the package was installed
Sources
- GitHub Advisory GHSA-f4mc-vj9p-gr25 · GitHub Advisory Database
Cite this entry
"Malware in @servicetitan/launchdarkly-service." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 4, 2026; last updated August 4, 2026. https://supplychainattack.org/incident/malware-in-servicetitan-launchdarkly-service-1hbxw9
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in sme-rko-finance-front-operations-special-payments (npm)
The npm package sme-rko-finance-front-operations-special-payments contained malicious code that downloads and executes platform-specific binaries from attacker-controlled infrastructure upon require(). The package employed obfuscation techniques to evade static analysis and included dual dropper paths in both index.js and lib/telemetry.js.
npmCompromised package - activecritical
Malware in bnpl-blocks-desktop-bnpl-anchor-title
Malware discovered in the npm package bnpl-blocks-desktop-bnpl-anchor-title. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malicious code in sme-rko-finance-front-operations-notifications-models (npm)
The npm package sme-rko-finance-front-operations-notifications-models contained malicious code that acts as a native-binary dropper, downloading and executing platform-specific binaries from attacker-controlled Cloudflare Workers domains and DNS fallback servers upon package require.
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-penalty (npm)
The npm package sme-rko-finance-front-operations-penalty contained malicious code that downloads and executes platform-specific binaries on require(). The dropper uses obfuscated string concatenation and DNS fallback channels to retrieve payloads from attacker-controlled infrastructure.
npmCompromised package