# GHSA-43vf-2x6g-p2m5: Malicious Package in browserift

> A malicious npm package executes remote commands, granting attackers full control over the host system.

- **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:** 2 Sep 2020

## What is GHSA-43vf-2x6g-p2m5?

GHSA-43vf-2x6g-p2m5 is a vulnerability in browserift, published on 2 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Version 16.3.3 of `browserift` contained malicious code as a preinstall script. The package was a backdoor that opened a connection to a remote server and executed incoming commands on both Unix and Windows machines

## Recommendation

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.

## Which versions are affected by GHSA-43vf-2x6g-p2m5?

2 open source packages ship an affected version, including browserift.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `browserift` | npm | All versions | None |
| `browserift` | npm | All versions | None |

## How do I fix GHSA-43vf-2x6g-p2m5?

No fix has been published for GHSA-43vf-2x6g-p2m5 yet. Limit exposure of the affected software until one is available.

## Is GHSA-43vf-2x6g-p2m5 being exploited?

There is no known exploitation of GHSA-43vf-2x6g-p2m5 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-43vf-2x6g-p2m5 and fix it if it is affected.

What it is: GHSA-43vf-2x6g-p2m5 is a vulnerability in browserift, published on 2 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-43vf-2x6g-p2m5 in the wild and no public exploit code.

Affected packages and fixed versions:
- browserift (npm): affected all versions; no fix listed
- browserift (npm): affected all versions; 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-43vf-2x6g-p2m5/ (Markdown: https://insights.sbomify.com/GHSA-43vf-2x6g-p2m5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-43vf-2x6g-p2m5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-43vf-2x6g-p2m5/
Summaries are generated and may contain mistakes; the official description above is the record.