# MAL-2026-15940: Malicious code in oce-configurator-wireless-frontend (npm)


- **Type:** Malicious package
- **Package:** `oce-configurator-wireless-frontend` (npm)
- **Published:** 6 Sep 2026

## What is MAL-2026-15940?

MAL-2026-15940 is a malicious package in oce-configurator-wireless-frontend, published on 6 Sep 2026. 

### Official description

Package name resembles an internal Swisscom OCE package and is published at version 9999.0.0 to win resolution against a private registry. The preinstall.js lifecycle script, which runs automatically on `npm install`, collects installer identifiers (os.hostname, os.userInfo().username, process.cwd, __dirname, package name/version, process.platform, node version, npm user-agent) and exfiltrates them to hardcoded external endpoints via three channels: (1) an HTTP/HTTPS POST to /beacon/<token> at the Interactsh collector dae7n4pijsh1ahi9684gu8get3kaiefc9.oast.online with a fallback from HTTPS to plain HTTP on error, (2) a plain-HTTP POST to the bare IP 5.189.159.252, and (3) a DNS side channel where each identifier is hex-encoded (Buffer.from(s).toString('hex').slice(0,60)) and concatenated as subdomain labels of the oast.online host, then resolved via dns.lookup. A hardcoded token 'swisscom-oce-3b9f1c7a2e' correlates the beaconed data with the targeted organization.

The OpenSSF Package Analysis project identified 'oce-configurator-wireless-frontend' @ 9999.0.0 (npm) as malicious.

It is considered malicious because:

- The package communicates with a domain associated with malicious activity.

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

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-15940 is a malicious package: oce-configurator-wireless-frontend (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-15940/ (Markdown: https://insights.sbomify.com/MAL-2026-15940/index.md)
```

## Sources

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

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