Which versions of dakumangalsingh_virus are malicious?

The following npm versions of dakumangalsingh_virus are flagged malicious: 1.0.0, 1.2.0, 1.3.0. Treat any of these as compromised.

How do I remediate dakumangalsingh_virus if I installed it?

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.

I already installed dakumangalsingh_virus — how do I know if it already compromised me?

If dakumangalsingh_virus was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is dakumangalsingh_virus part of a known attack campaign?

Yes — dakumangalsingh_virus is associated with the GHSA-ppp3-vpgx-2v73, IN-MAL-2026-017480, IN-MAL-2026-017478, IN-MAL-2026-017479 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find dakumangalsingh_virus across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dakumangalsingh_virus (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dakumangalsingh_virus across your stack and pipelines.

Malicious package

dakumangalsingh_virusnpm

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)

MAL-2026-13761

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall dakumangalsingh_virus

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

3 flagged

1.0.01.2.01.3.0

Indicators of compromise (SHA-256)

1fefea2058bd447b1775b883d645b9cd3c74943a8fad9acb0f997d388140c9b0

18035544490cb6f604425bbc4a843cfa9ad5f0a125e6be45f5b57e8a51d18914

3213de7a5349b7072a0a5d4ed866d1042ceafd11778a50fd3a603e642ba2f063

f5c32842af81f239247b0cb4980f29b20051e92fed5751d4c297ede4f5a9116d

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dakumangalsingh_virus (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dakumangalsingh_virus across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks dakumangalsingh_virus before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. dakumangalsingh_virus on npm has been identified as a malicious package (versions 1.0.0, 1.2.0, 1.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-ppp3-vpgx-2v73IN-MAL-2026-017480IN-MAL-2026-017478IN-MAL-2026-017479

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database