lwc-slds-lbcnpm
lwc-slds-lbc is a confirmed malicious npm package (MAL-2026-10923) that executes malicious code on install (malicious version 18.9.41). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in lwc-slds-lbc (npm)
What this malware does
package.json declares a preinstall script that executes examples/verify.js on npm install. verify.js invokes setUserFromPublicIp() from src/index.js, which fetches the installer's public egress IP from Cloudflare's cdn-cgi/trace endpoint, initializes Sentry with a hardcoded author-controlled DSN at o4510485815754752.ingest.us.sentry.io (project 4511716882972672), attaches the IP as the Sentry user ip_address, deliberately triggers an error via buggyFunction(), and flushes the event so the installer's IP and host telemetry are transmitted before any user code runs. Additionally, src/index.js's exported init()/check()/wrap() API falls back to the same hardcoded DSN when neither options.dsn nor process.env.SENTRY_DSN is set and enables sendDefaultPii: true, so consumers following the README route their application's exception data (including PII such as IP addresses) to the author's Sentry project by default.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for lwc-slds-lbc (version 18.9.41). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lwc-slds-lbc across your stack and pipelines.
If you installed it — respond
Remove lwc-slds-lbc 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 lwc-slds-lbc 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 lwc-slds-lbc 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks lwc-slds-lbc-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.