Malicious code in seapy-ops (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 seapy-ops
- Affected
- >= 1.0.0, <= 1.0.0>= 1.0.1, <= 1.0.1>= 1.0.2, <= 1.0.2>= 1.1.0, <= 1.1.0>= 1.1.1, <= 1.1.1>= 1.1.2, <= 1.1.2>= 1.2.1, <= 1.2.1>= 1.2.2, <= 1.2.2
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-17880 lists affected ranges: PyPI seapy-ops >=1.0.0 =1.0.1 =1.0.2 =1.1.0 =1.1.1 =1.1.2 =1.2.1 =1.2.2 <=1.2.2
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.
In seapy-ops versions 1.0.0, 1.0.1, 1.0.2, 1.1.0, 1.1.1, and 1.1.2, an advertised local file analysis tool conceals folder collection and upload commands behind an unlock gate. Once unlocked, it recursively uploads eligible files from the working directory to a configured remote server; a hidden prompt command also uploads the folder before sending the first prompt. File symlinks can expose content outside that directory. Server-supplied result paths additionally allow files to be written outside the working directory. Versions 1.2.1 and 1.2.2 instead present a Python REPL that silently sends eligible single-token input to the server as an unlock password, subject to filtering and attempt limits. Other commands, excluding local help, version, unlock, configuration, and uninstall paths, can fetch Base64-encoded, gzip-compressed code, execute it in memory, and call its main function. Loader errors are disguised as Python file-not-found errors. The malicious assessment is based on…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from osv record MAL-2026-17880
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-17880 Advisory: Malicious code in seapy-ops (PyPI) IDs: mal-2026-17880 Record: https://patchnext.com/advisories/mal-2026-17880 (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 seapy-ops: affected >= 1.0.0, <= 1.0.0; >= 1.0.1, <= 1.0.1; >= 1.0.2, <= 1.0.2; >= 1.1.0, <= 1.1.0; >= 1.1.1, <= 1.1.1; >= 1.1.2, <= 1.1.2; >= 1.2.1, <= 1.2.1; >= 1.2.2, <= 1.2.2 ## Suggested inspection (read-only) - `python -m pip show seapy-ops`: 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 seapy-ops. - 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-17880 (OSV record MAL-2026-17880 lists affected ranges: PyPI seapy-ops >=1.0.0 =1.0.1 =1.0.2 =1.1.0 =1.1.1 =1.1.2 =1.2.1 =1.2.2 <=1.2.2) Commands are suggestions: review each one before running it.
Loading voting…