dakumangalsingh_virusnpm
Advisory published Updated
dakumangalsingh_virus is a confirmed malicious npm package (MAL-2026-13761) that opens a backdoor for remote access (malicious versions 1.0.0, 1.2.0, 1.3.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in dakumangalsingh_virus (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for dakumangalsingh_virus (3 malicious versions).
If you installed it — respond
dakumangalsingh_virus establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If dakumangalsingh_virus was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks dakumangalsingh_virus-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.