# GHSA-377f-vvrc-9wgg: Malicious Package in zemen

> A malicious npm package steals sensitive form data like passwords and credit card numbers by sending them to an external server.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Sep 2020

## What is GHSA-377f-vvrc-9wgg?

GHSA-377f-vvrc-9wgg is a vulnerability in zemen, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Version 0.0.5 of `zemen` contained malicious code. The code when executed in the browser would enumerate password, cvc, cardnumber fields from forms and send the extracted values to `https://js-metrics.com/minjs.php?pl=`

## Recommendation

Remove the package from your environment. It's also recommended to evaluate your application to determine whether or not user data was compromised.

## Which versions are affected by GHSA-377f-vvrc-9wgg?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zemen` | npm | From 0.0.5 | 0.0.6 |
| `zemen` | npm | From 0.0.5 | 0.0.6 |

## How do I fix GHSA-377f-vvrc-9wgg?

Upgrade zemen to 0.0.6 or later.

## Is GHSA-377f-vvrc-9wgg being exploited?

There is no known exploitation of GHSA-377f-vvrc-9wgg in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-377f-vvrc-9wgg and fix it if it is affected.

What it is: GHSA-377f-vvrc-9wgg is a vulnerability in zemen, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-377f-vvrc-9wgg in the wild and no public exploit code.

Affected packages and fixed versions:
- zemen (npm): affected from 0.0.5; fixed in 0.0.6
- zemen (npm): affected from 0.0.5; fixed in 0.0.6

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-377f-vvrc-9wgg/ (Markdown: https://insights.sbomify.com/GHSA-377f-vvrc-9wgg/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-377f-vvrc-9wgg

---
From sbomify Insights: https://insights.sbomify.com/GHSA-377f-vvrc-9wgg/
Summaries are generated and may contain mistakes; the official description above is the record.