# GHSA-3cjv-4phw-gvvv: Malicious Package in getcookies

> A backdoor in the getcookies npm package allows remote attackers to execute arbitrary commands on affected systems.

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

## What is GHSA-3cjv-4phw-gvvv?

GHSA-3cjv-4phw-gvvv is a vulnerability in getcookies, published on 1 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The `getcookies` module contained a backdoor that would allow for a remote attacker to execute arbitrary commands on the system running the malicious module.

## Recommendation

This module should be uninstalled if found used within an application. In addition to removing the installed module, you will also want to evaluate your application to determine whether or not user data or systems were compromised.

## Which versions are affected by GHSA-3cjv-4phw-gvvv?

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


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

## How do I fix GHSA-3cjv-4phw-gvvv?

No fix has been published for GHSA-3cjv-4phw-gvvv yet. Limit exposure of the affected software until one is available.

## Is GHSA-3cjv-4phw-gvvv being exploited?

There is no known exploitation of GHSA-3cjv-4phw-gvvv in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-3cjv-4phw-gvvv and fix it if it is affected.

What it is: GHSA-3cjv-4phw-gvvv is a vulnerability in getcookies, published on 1 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-3cjv-4phw-gvvv in the wild and no public exploit code.

Affected packages and fixed versions:
- getcookies (npm): affected all versions; no fix listed
- getcookies (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-3cjv-4phw-gvvv/ (Markdown: https://insights.sbomify.com/GHSA-3cjv-4phw-gvvv/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-3cjv-4phw-gvvv

---
From sbomify Insights: https://insights.sbomify.com/GHSA-3cjv-4phw-gvvv/
Summaries are generated and may contain mistakes; the official description above is the record.