Malicious Package in soket.js

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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.

Published by the source

1 Sep 2020, 21:14 UTC

Last modified by the source

9 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 12:08 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-x6gq-467r-hwcc

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-x6gq-467r-hwcc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-x6gq-467r-hwcc

Advisory: Malicious Package in soket.js
IDs: GHSA-x6gq-467r-hwcc
Record: https://patchnext.com/advisories/ghsa-x6gq-467r-hwcc (revision 2, source checked 26 Oct 2026, 12:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm soket.js: affected every version

## Suggested inspection (read-only)
- `npm ls soket.js --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on soket.js.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-x6gq-467r-hwcc (OSV record GHSA-x6gq-467r-hwcc lists affected ranges: npm soket.js >=0)
- Verified: https://github.com/advisories/GHSA-x6gq-467r-hwcc (GitHub-reviewed advisory GHSA-x6gq-467r-hwcc lists affected ranges: npm soket.js >=0)

Commands are suggestions: review each one before running it.