# GHSA-vv52-3mrp-455m: Malicious Package in m-backdoor

> The m-backdoor npm package contains malicious code that executes remote scripts, allowing attackers to modify website content and execute arbitrary code.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2020

## What is GHSA-vv52-3mrp-455m?

GHSA-vv52-3mrp-455m is a vulnerability in m-backdoor, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by GHSA-vv52-3mrp-455m?

2 open source packages ship an affected version, including m-backdoor.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `m-backdoor` | npm | From 0.0.0 | None |
| `m-backdoor` | npm | From 0.0.0 | None |

## How do I fix GHSA-vv52-3mrp-455m?

No fix has been published for GHSA-vv52-3mrp-455m yet. Limit exposure of the affected software until one is available.

## Is GHSA-vv52-3mrp-455m being exploited?

There is no known exploitation of GHSA-vv52-3mrp-455m in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-vv52-3mrp-455m and fix it if it is affected.

What it is: GHSA-vv52-3mrp-455m is a vulnerability in m-backdoor, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-vv52-3mrp-455m in the wild and no public exploit code.

Affected packages and fixed versions:
- m-backdoor (npm): affected from 0.0.0; no fix listed
- m-backdoor (npm): affected from 0.0.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-vv52-3mrp-455m/ (Markdown: https://insights.sbomify.com/GHSA-vv52-3mrp-455m/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-vv52-3mrp-455m

---
From sbomify Insights: https://insights.sbomify.com/GHSA-vv52-3mrp-455m/
Summaries are generated and may contain mistakes; the official description above is the record.