# MAL-2026-4464: Malicious code in @vtmn-play/react (npm)


- **Type:** Malicious package
- **Package:** `@vtmn-play/react` (npm)
- **Published:** 20 May 2026
- **Also known as:** GHSA-vpcv-xpqm-w228

## What is MAL-2026-4464?

MAL-2026-4464 is a malicious package in @vtmn-play/react, published on 20 May 2026. 

### Official description

Package name @vtmn-play/react mimics Decathlon's Vitamin design system @vtmn/react and is published at version 99.9.1, the canonical dependency-confusion version-bump shape used to override an internal package on installer machines. The package's own code is an empty stub (module.exports = {}). package.json declares a dependency `ltidisafe` resolved from a non-registry tarball URL: https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.3.2.tgz — the path segment `depenconf` explicitly advertises dependency-confusion intent. On `npm install`, npm fetches and installs that arbitrary tarball from a generic Google Cloud Storage bucket unrelated to Decathlon, dragging attacker-controlled code into the installer's dependency tree. The stub-host pattern combined with an off-registry tarball whose URL is self-labeled with the attack name leaves no benign interpretation.

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.

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

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

## Sources

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

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