# MAL-2026-18213: Malicious code in @cecm-web-sdk/core (npm)


- **Type:** Malicious package
- **Package:** `@cecm-web-sdk/core` (npm)
- **Published:** 23 Oct 2026
- **Also known as:** GHSA-88qx-q5v7-q7x5

## What is MAL-2026-18213?

MAL-2026-18213 is a malicious package in @cecm-web-sdk/core, published on 23 Oct 2026. 

### Official description

The package has no functional code: its declared main (index.js) exports a Proxy whose property access returns no-op functions, and the package describes itself as a 'Compatibility shim'. On npm install, the postinstall lifecycle hook (`node beacon.cjs`) runs and POSTs a payload containing the package name, OS hostname, install directory, current working directory, and Node version to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc over plain HTTP. index.js additionally invokes beacon.cjs::fire() at top level, so requiring or importing the module triggers the same beacon a second time, which fires even when installs run with --ignore-scripts. The scope-prefixed name combined with host/path identification is the canonical dependency-confusion recon success-ping, enabling the operator of 185.158.107.175 to identify internal hosts and project paths where this name resolves to the public registry copy.

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

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

## Sources

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

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