# MAL-2026-13761: Malicious code in dakumangalsingh_virus (npm)


- **Type:** Malicious package
- **Package:** `dakumangalsingh_virus` (npm)
- **Published:** 11 Aug 2026
- **Also known as:** GHSA-ppp3-vpgx-2v73

## What is MAL-2026-13761?

MAL-2026-13761 is a malicious package in dakumangalsingh_virus, published on 11 Aug 2026. 

### Official description

The tarball contains a 455 KB Windows PE64 executable named DakuMangalSingh.exe (sha256 368320791e5c022ffabedb44eae6ca902fe3f524754a085b726617c2006dc791) alongside a zero-byte index.js. package.json declares no preinstall/install/postinstall/prepare lifecycle scripts and its main entry is empty, so neither npm install nor require() of the package causes the binary to be executed, decoded, or written elsewhere. The package name self-labels as a virus, and no documentation, source, or purpose is provided for the shipped binary. Installing or importing this package in a normal npm pipeline does not run the executable; harm would only occur if a user were separately induced to launch DakuMangalSingh.exe on a Windows host.

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

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

## Sources

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

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