# MAL-2026-10923: Malicious code in lwc-slds-lbc (npm)


- **Type:** Malicious package
- **Package:** `lwc-slds-lbc` (npm)
- **Published:** 20 Jul 2026
- **Also known as:** GHSA-xm8f-w286-57x5

## What is MAL-2026-10923?

MAL-2026-10923 is a malicious package in lwc-slds-lbc, published on 20 Jul 2026. 

### Official description

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.

## What should I do about MAL-2026-10923?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-10923 is a malicious package: lwc-slds-lbc (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-10923/ (Markdown: https://insights.sbomify.com/MAL-2026-10923/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-10923

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-10923/
Summaries are generated and may contain mistakes; the official description above is the record.