Critical Vulnerability in malicious-npm-package

malicious-npm-package Updated 02 Oct 2025

Summary

04/09/2020
CRITICAL
No i
Critical
9.8

GHSA-49c6-3wr4-8jr4: Malicious Package in malicious-npm-package. Affects malicious-npm-package versions >= 0.0.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

malicious-npm-package is an open-source npm package that contains malicious code targeting Windows systems. It poses a significant security risk as it executes a PowerShell command to download and run an executable file from a remote server. This package should be considered compromised, and immediate action is required to mitigate the potential damage caused by the malware.

Vulnerability Detail

The malicious-npm-package, in all versions, contains code that can compromise the security of Windows systems. When installed or running, the package executes a PowerShell command that downloads an executable file from a remote server. This action grants full control of the affected computer to an external entity. As a result, all secrets and keys stored on the compromised computer should be rotated immediately from a different computer. Although removing the package is recommended, it may not guarantee the removal of all malicious software installed as a consequence of its installation.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to follow the recommended steps to fix the issue and mitigate the potential damage caused by the malicious-npm-package.

Conclusion

The critical vulnerability in malicious-npm-package poses a significant security risk to Windows systems. Immediate action is required to mitigate the potential damage caused by the malware. Rotate all compromised secrets and keys, remove the package, and conduct a thorough security audit. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for malicious-npm-package →

Share this vulnerability

FAQ

malicious-npm-package is an open-source npm package that contains malicious code targeting Windows systems.

The vulnerability in malicious-npm-package allows an external entity to gain full control of your computer, compromising the security of your system and potentially accessing any stored secrets and keys.

If you have malicious-npm-package installed, consider your computer fully compromised. Rotate all secrets and keys stored on that computer from a different, secure computer. Remove the malicious-npm-package and conduct a thorough security audit.

Removing the malicious-npm-package is recommended, but it may not guarantee the removal of all malicious software that may have been installed as a consequence of its installation. A thorough security audit is necessary to identify any additional malicious software.

To protect your computer from similar vulnerabilities, regularly update your software packages, use reputable sources for package installations, and conduct security audits to identify and address any potential risks.

Related vulnerabilities

Recent vulnerabilities recorded for malicious-npm-package.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback