# MAL-2026-15942: Malicious code in omni-channel-order-frontend (npm)


- **Type:** Malicious package
- **Package:** `omni-channel-order-frontend` (npm)
- **Published:** 6 Sep 2026

## What is MAL-2026-15942?

MAL-2026-15942 is a malicious package in omni-channel-order-frontend, published on 6 Sep 2026. 

### Official description

The package name and 9999.0.0 version are consistent with a dependency-confusion lure targeting an internal `omni-channel-order-frontend` package. `package.json` declares a `preinstall` script (`preinstall.js`) that fires automatically on `npm install`. On execution it collects installer identifiers — `os.hostname()`, `os.userInfo().username`, current working directory, install path, `process.platform`/OS release, Node version, npm user-agent, and the resolved package name+version — and transmits them to hardcoded external destinations via three channels: a hex-encoded DNS-subdomain lookup to the Interactsh OAST collector `dae7n4pijsh1ahi9684gu8get3kaiefc9.oast.online`, an HTTPS POST to the same OAST host, and a plain-HTTP POST to the bare IP `5.189.159.252`. Identifiers are hex-encoded into DNS labels so the fields still reach the attacker's authoritative resolver when HTTP egress is blocked. A `swisscom-oce-*` token embedded in the beacon tags the victim organization. Self-labeling in the source as an authorized bug-bounty PoC is author-controlled text and is inconsistent with a public-registry release using an implausibly high version number to win dependency resolution against an internal package.

The OpenSSF Package Analysis project identified 'omni-channel-order-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-15942?

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-15942 is a malicious package: omni-channel-order-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-15942/ (Markdown: https://insights.sbomify.com/MAL-2026-15942/index.md)
```

## Sources

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

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