# MAL-2026-6702: Malicious code in vue-demi-fix (npm)


- **Type:** Malicious package
- **Package:** `vue-demi-fix` (npm)
- **Published:** 30 Jun 2026
- **Also known as:** GHSA-p53q-mf26-4h26

## What is MAL-2026-6702?

MAL-2026-6702 is a malicious package in vue-demi-fix, published on 30 Jun 2026. 

### Official description

vue-demi-fix is a name-confusion package against the widely used vue-demi library. package.json declares both preinstall and postinstall lifecycle scripts that invoke curl against a hardcoded bare-IP HTTP endpoint (http://109.71.252.153:8080/), exfiltrating the installer's OS, username (whoami), current working directory (pwd), and hostname as URL query parameters on every npm install. The package ships no real functionality — index.js only prints a proof-of-concept notice and README self-labels as a 'Responsible Disclosure' PoC. Regardless of the PoC framing, installers receive no benign function and their host identity is unconditionally beaconed to a non-publisher, non-registry endpoint on a default install.

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.

The OpenSSF Package Analysis project identified 'vue-demi-fix' @ 10.0.4 (npm) as malicious.

It is considered malicious because:

- The package executes one or more commands associated with malicious behavior.

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

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-6702 is a malicious package: vue-demi-fix (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-6702/ (Markdown: https://insights.sbomify.com/MAL-2026-6702/index.md)
```

## Sources

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

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