Malicious code in soundsocket (PyPI)
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
PyPI soundsocket
- Affected
- >= 0.1.0, <= 0.1.0
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-18165 lists affected ranges: PyPI soundsocket >=0.1.0 <=0.1.0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
--- _-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (17292086eb906d22ce89e72fb3d6f1bd9edf44d8bb7a7caa319cee80ee6381bb) No install-time or import-time behavior consistent with credential access, outbound exfiltration, remote code fetch/execution, persistence, or silent-relay was observed in this package version. No lifecycle hooks performing network I/O, no.pth side effects beyond sys.path handling, and no top-level subprocess/network activity were identified in the shipped files.
Source: kam193 (9b50b12b54ecdc99f678332cf4a8e2d333ce5398c1c545eb994d2f368843cb03) This campaign consists of similar loader packages, which provide executing code from a given URL. While they do not contain the malicious payload and the usage remains unknown, they are clearly a coordinated campaign to place multiple deceptive ways to load malicious code. --- Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign:…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from osv record MAL-2026-18165
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: mal-2026-18165 Advisory: Malicious code in soundsocket (PyPI) IDs: mal-2026-18165 Record: https://patchnext.com/advisories/mal-2026-18165 (revision 1, source checked 30 Oct 2026, 06:40 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated 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 - PyPI soundsocket: affected >= 0.1.0, <= 0.1.0 ## Suggested inspection (read-only) - `python -m pip show soundsocket`: prints the installed version. Run with the environment that serves production active. ## 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 soundsocket. - 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/MAL-2026-18165 (OSV record MAL-2026-18165 lists affected ranges: PyPI soundsocket >=0.1.0 <=0.1.0) Commands are suggestions: review each one before running it.
Loading voting…