Malicious code in dakumangalsingh_virus (npm)
The npm package dakumangalsingh_virus contains a 455 KB Windows PE64 executable named DakuMangalSingh.exe. The package itself does not execute the binary during installation or import, as no lifecycle scripts or entry points trigger it. However, if a user manually executes the binary on a Windows system, it may cause harm. The package self-identifies as a virus and lacks documentation or source code. Systems with this package installed should be considered fully compromised, and all secrets and keys should be rotated from a clean environment.
AI Analysis
Technical Summary
The dakumangalsingh_virus npm package includes a malicious Windows executable (DakuMangalSingh.exe) alongside an empty index.js and no lifecycle scripts, meaning normal npm install or require() actions do not trigger execution. The package name explicitly labels it as a virus, and no legitimate functionality or source code is provided. According to the ghsa-malware source, any system with this package installed or running is considered fully compromised, necessitating immediate secret rotation and package removal. However, removal may not fully eliminate the threat due to potential persistent malicious activity initiated by the executable if run.
Potential Impact
If the DakuMangalSingh.exe binary is manually executed on a Windows host, the system may become fully compromised, potentially allowing an attacker full control. All stored secrets and keys on the affected system are at risk and should be rotated immediately from a different, trusted machine. Simply installing or importing the package does not cause harm, but the presence of the malicious binary poses a severe risk if executed.
Mitigation Recommendations
Users should immediately remove the dakumangalsingh_virus package from any systems where it is installed. Because the package contains a malicious executable that can fully compromise a system if run, all secrets and keys stored on affected machines should be rotated from a clean environment. There is no indication of an official patch or fix; remediation involves removal and secret rotation. Normal npm install or require() does not execute the malicious binary, so avoid manually running the executable. Monitor for any signs of compromise and consider rebuilding affected systems.
Malicious code in dakumangalsingh_virus (npm)
Description
The npm package dakumangalsingh_virus contains a 455 KB Windows PE64 executable named DakuMangalSingh.exe. The package itself does not execute the binary during installation or import, as no lifecycle scripts or entry points trigger it. However, if a user manually executes the binary on a Windows system, it may cause harm. The package self-identifies as a virus and lacks documentation or source code. Systems with this package installed should be considered fully compromised, and all secrets and keys should be rotated from a clean environment.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The dakumangalsingh_virus npm package includes a malicious Windows executable (DakuMangalSingh.exe) alongside an empty index.js and no lifecycle scripts, meaning normal npm install or require() actions do not trigger execution. The package name explicitly labels it as a virus, and no legitimate functionality or source code is provided. According to the ghsa-malware source, any system with this package installed or running is considered fully compromised, necessitating immediate secret rotation and package removal. However, removal may not fully eliminate the threat due to potential persistent malicious activity initiated by the executable if run.
Potential Impact
If the DakuMangalSingh.exe binary is manually executed on a Windows host, the system may become fully compromised, potentially allowing an attacker full control. All stored secrets and keys on the affected system are at risk and should be rotated immediately from a different, trusted machine. Simply installing or importing the package does not cause harm, but the presence of the malicious binary poses a severe risk if executed.
Mitigation Recommendations
Users should immediately remove the dakumangalsingh_virus package from any systems where it is installed. Because the package contains a malicious executable that can fully compromise a system if run, all secrets and keys stored on affected machines should be rotated from a clean environment. There is no indication of an official patch or fix; remediation involves removal and secret rotation. Normal npm install or require() does not execute the malicious binary, so avoid manually running the executable. Monitor for any signs of compromise and consider rebuilding affected systems.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13761
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-ppp3-vpgx-2v73"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7c9b46bf8831d539cdd174
Added to database: 08/12/2026, 16:11:50 UTC
Last enriched: 08/12/2026, 16:48:47 UTC
Last updated: 08/12/2026, 16:48:47 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.