Vulnerabilities in pkg:npm/m-backdoor

PACKAGE
Share
Advisory Summary

GHSA-vv52-3mrp-455m is a CRITICAL malicious package vulnerability (CWE-506: Embedded Malicious Code) affecting M backdoor libraries in the npm ecosystem. The issue involves malicious package in m-backdoor. Remediation is available in the latest vendor maintenance releases.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/m-backdoor

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/m-backdoor. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-vv52-3mrp-455m - CRITICAL Malicious Package in m-backdoor

GHSA-vv52-3mrp-455m at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-vv52-3mrp-455m
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-506: Embedded Malicious Code
Affected Product M backdoor
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-vv52-3mrp-455m

To remediate this vulnerability, upgrade all affected M backdoor dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

m-backdoor fixed: Latest secure release 
npm install m-backdoor@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls m-backdoor

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-vv52-3mrp-455m, inspect your project dependencies using npm:

npm ls m-backdoor

Analyze the terminal output to locate any version of M backdoor in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The npm ls m-backdoor command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-506: Embedded Malicious Code, where the product contains code that appears to be malicious in nature. In M backdoor, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

All versions of `m-backdoor` contain malicious code. The package downloads a file from a remote server and executes it as a preinstall script. At the time of the release of this advisory the downloaded file only defaces websites by removing elements randomly from the DOM. ## Recommendation Remove the package from your system.

GHSA-vv52-3mrp-455m Affected M backdoor Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
m-backdoor
npm/m-backdoor
npm
≥ 0.0.0

References

www.npmjs.com/advisories/1513 WEB
https://www.npmjs.com/advisories/1513

Frequently Asked Questions

What is GHSA-vv52-3mrp-455m?
GHSA-vv52-3mrp-455m is a security vulnerability in M backdoor involving Malicious Package in m-backdoor under CWE-506: Embedded Malicious Code.
Which M backdoor versions are affected?
Affected versions include releases prior to current release patches across affected packages: m-backdoor.
What version fixes GHSA-vv52-3mrp-455m?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is m-backdoor affected?
Yes, m-backdoor is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What CWE is associated with GHSA-vv52-3mrp-455m?
GHSA-vv52-3mrp-455m is classified under CWE-506: Embedded Malicious Code (The product contains code that appears to be malicious in nature.).
How can I check npm dependencies for GHSA-vv52-3mrp-455m?
Run the dependency tree command: 'npm ls m-backdoor'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-vv52-3mrp-455m",
  "modified" : "2020-08-31T19:01:56Z",
  "published" : "2020-09-03T15:53:36Z",
  "aliases" : [ ],
  "summary" : "Malicious Package in m-backdoor",
  "details" : "All versions of `m-backdoor` contain malicious code. The package downloads a file from a remote server and executes it as a preinstall script. At the time of the release of this advisory the downloaded file only defaces websites by removing elements randomly from the DOM. \n\n\n## Recommendation\n\nRemove the package from your system.",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "m-backdoor"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/advisories/1513"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-506" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2020-08-31T19:01:56Z",
    "nvd_published_at" : null
  }
}