# MAL-2026-5890: Malicious code in @dsft/ft-utils (npm)


- **Type:** Malicious package
- **Package:** `@dsft/ft-utils` (npm)
- **Published:** 16 Jun 2026
- **Also known as:** GHSA-2578-g4v9-hc4p

## What is MAL-2026-5890?

MAL-2026-5890 is a malicious package in @dsft/ft-utils, published on 16 Jun 2026. 

### Official description

The package is a dependency-confusion proof-of-concept squatting on the @dsft/ scope. Its package.json declares a preinstall hook that runs index.js, which reads the installer's INIT_CWD environment variable (the consumer's project directory), derives the project's basename, and POSTs it together with a package identifier and timestamp to a hardcoded third-party URL (https://deepbounty.dd06-dev.fr/cb/f9543624-20d8-465b-a026-d01872b93933). The package provides no library functionality matching its name; the install-time beacon is its sole behavior, and the package self-describes as a 'Security PoC for Bug Bounty.' Any `npm install` of this package automatically discloses the installing project's directory name and confirms the host's environment to the operator of the callback endpoint, without consent.

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-5890?

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

## Sources

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

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