# GHSA-m794-qv59-gj7c: Malicious Package in signqle

> A malicious npm package exfiltrates cryptocurrency wallets, requiring immediate key rotation and system remediation for affected users.

- **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:** No
- **Published:** 3 Sep 2020

## What is GHSA-m794-qv59-gj7c?

GHSA-m794-qv59-gj7c is a vulnerability in signqle, 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

All versions of this package contained malware. The package was designed to find and exfiltrate cryptocurrency wallets.

## 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-m794-qv59-gj7c?

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


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

## How do I fix GHSA-m794-qv59-gj7c?

No fix has been published for GHSA-m794-qv59-gj7c yet. Limit exposure of the affected software until one is available.

## Is GHSA-m794-qv59-gj7c being exploited?

There is no known exploitation of GHSA-m794-qv59-gj7c in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-m794-qv59-gj7c and fix it if it is affected.

What it is: GHSA-m794-qv59-gj7c is a vulnerability in signqle, 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-m794-qv59-gj7c in the wild and no public exploit code.

Affected packages and fixed versions:
- signqle (npm): affected from 0.0.0; no fix listed
- signqle (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-m794-qv59-gj7c/ (Markdown: https://insights.sbomify.com/GHSA-m794-qv59-gj7c/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-m794-qv59-gj7c

---
From sbomify Insights: https://insights.sbomify.com/GHSA-m794-qv59-gj7c/
Summaries are generated and may contain mistakes; the official description above is the record.