# GHSA-fw76-p9p2-6pvf: Malicious Package in serilize

> A malicious npm package exfiltrates system information to a remote server, requiring immediate removal from the environment.

- **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-fw76-p9p2-6pvf?

GHSA-fw76-p9p2-6pvf is a vulnerability in serilize, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This package contained malicious code. The package uploaded system information such as OS and hostname to a remote server.

## Recommendation

Remove the package from your environment. There are no indications of further compromise.

## Which versions are affected by GHSA-fw76-p9p2-6pvf?

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


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

## How do I fix GHSA-fw76-p9p2-6pvf?

No fix has been published for GHSA-fw76-p9p2-6pvf yet. Limit exposure of the affected software until one is available.

## Is GHSA-fw76-p9p2-6pvf being exploited?

There is no known exploitation of GHSA-fw76-p9p2-6pvf in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-fw76-p9p2-6pvf and fix it if it is affected.

What it is: GHSA-fw76-p9p2-6pvf is a vulnerability in serilize, 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-fw76-p9p2-6pvf in the wild and no public exploit code.

Affected packages and fixed versions:
- serilize (npm): affected from 0.0.0; no fix listed
- serilize (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-fw76-p9p2-6pvf/ (Markdown: https://insights.sbomify.com/GHSA-fw76-p9p2-6pvf/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-fw76-p9p2-6pvf

---
From sbomify Insights: https://insights.sbomify.com/GHSA-fw76-p9p2-6pvf/
Summaries are generated and may contain mistakes; the official description above is the record.