# MAL-2026-18319: Malicious code in @sxm-web/client-sdk-core (npm)


- **Type:** Malicious package
- **Package:** `@sxm-web/client-sdk-core` (npm)
- **Published:** 23 Oct 2026
- **Also known as:** GHSA-v3mw-7pg4-rp68

## What is MAL-2026-18319?

MAL-2026-18319 is a malicious package in @sxm-web/client-sdk-core, published on 23 Oct 2026. 

### Official description

@sxm-web/client-sdk-core is a dependency-confusion package: it is described as a "Compatibility shim", uses inflated version numbers, and its README calls it an "authorized dependency-confusion test". Each listed version (0.0.1, 1.0.0, 1.0.1, 2.0.0, 1.1.0, 3.0.0, 13.3.7) has a postinstall script that runs `node beacon.cjs` on npm install, and index.js calls the same code when the package is imported; it POSTs the hostname, install path and current working directory over plain HTTP to `http://185.158.107.175:8787/_ah/dc`, and index.js exports a Proxy that returns no-op functions so builds importing the real package keep running. The npm account wiseke published 14 such packages under the @greenlake, @sxm-web, @drone-js-ext and @ppa-web-components scopes between 2026-10-23 21:23 and 2026-10-25 14:28 UTC; index.js is byte-identical to that of ph-common (MAL-2026-1809), which sends to the same endpoint.

@sxm-web/client-sdk-core@1.0.1 is a stub package whose only functional code is a beacon. The declared postinstall script runs `node beacon.cjs`, and the same beacon is also invoked at require time from index.js. The beacon collects installer-side identifiers (hostname, install path, current working directory, Node.js version, package name) and POSTs them in cleartext over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc, which is unrelated to any legitimate registry or publisher infrastructure. The package's `main` returns a Proxy that produces no-op functions for every accessed property, so the package provides no advertised functionality — the install itself is the payload. The scoped name `@sxm-web/client-sdk-core` combined with a `Compatibility shim` description is consistent with a dependency-confusion probe aimed at an internal/private SDK namespace, where the beacon's purpose is to confirm successful resolution against private names and to disclose the resolving host's identity and filesystem layout to the operator at the bare IP.

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-18319?

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-18319 is a malicious package: @sxm-web/client-sdk-core (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-18319/ (Markdown: https://insights.sbomify.com/MAL-2026-18319/index.md)
```

## Sources

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

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