# MAL-2026-15941: Malicious code in ocfe-tv-subscription-center-web (npm)


- **Type:** Malicious package
- **Package:** `ocfe-tv-subscription-center-web` (npm)
- **Published:** 6 Sep 2026

## What is MAL-2026-15941?

MAL-2026-15941 is a malicious package in ocfe-tv-subscription-center-web, published on 6 Sep 2026. 

### Official description

Package name resembles an internal-scoped name and uses an implausibly high version (9999.0.0) consistent with dependency-confusion targeting. The preinstall.js lifecycle script runs automatically on `npm install` and collects installer identifiers (os.hostname, os.userInfo().username, cwd, __dirname, platform/os.release, node version, npm user-agent, resolved package name and version) and transmits them through three channels to author-controlled destinations: a DNS lookup whose subdomain labels are hex-encoded fields (token, package name, hostname, username) appended to dae7n4pijsh1ahi9684gu8get3kaiefc9.oast.online, an HTTPS POST to the same interactsh host, and an HTTP POST to the bare IP 5.189.159.252. The DNS channel provides a covert side-channel that bypasses HTTP-only egress filtering. A self-labelled 'bug bounty research' header in the file does not change the behavior: installing this package causes installer-side identifiers to leave the machine to hardcoded, non-configurable endpoints.

The OpenSSF Package Analysis project identified 'ocfe-tv-subscription-center-web' @ 0.0.1 (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-15941?

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-15941 is a malicious package: ocfe-tv-subscription-center-web (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-15941/ (Markdown: https://insights.sbomify.com/MAL-2026-15941/index.md)
```

## Sources

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

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