# GHSA-x6gq-467r-hwcc: Malicious Package in soket.js

> Malicious npm package executes arbitrary commands via C2 server, requiring credential rotation and system reinstallation.

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

## What is GHSA-x6gq-467r-hwcc?

GHSA-x6gq-467r-hwcc is a vulnerability in soket.js, published on 1 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 `soket.js` are considered malicious. The package is malware designed to take advantage of users making a mistake when typing the name of a module to install. When executed, the package calls home to a Command and Control server to execute arbitrary commands.

## Recommendation

This package was published to the npm Registry for a very short period of time. If you happen to find it in your environment you should revoke and rotate all credentials  found on the compromised machine, as well as completely erase the affected machine and reinstall your Operating System.

## Which versions are affected by GHSA-x6gq-467r-hwcc?

2 open source packages ship an affected version, including soket.js.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `soket.js` | npm | All versions | None |
| `soket.js` | npm | All versions | None |

## How do I fix GHSA-x6gq-467r-hwcc?

No fix has been published for GHSA-x6gq-467r-hwcc yet. Limit exposure of the affected software until one is available.

## Is GHSA-x6gq-467r-hwcc being exploited?

There is no known exploitation of GHSA-x6gq-467r-hwcc in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-x6gq-467r-hwcc and fix it if it is affected.

What it is: GHSA-x6gq-467r-hwcc is a vulnerability in soket.js, published on 1 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-x6gq-467r-hwcc in the wild and no public exploit code.

Affected packages and fixed versions:
- soket.js (npm): affected all versions; no fix listed
- soket.js (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-x6gq-467r-hwcc/ (Markdown: https://insights.sbomify.com/GHSA-x6gq-467r-hwcc/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-x6gq-467r-hwcc

---
From sbomify Insights: https://insights.sbomify.com/GHSA-x6gq-467r-hwcc/
Summaries are generated and may contain mistakes; the official description above is the record.