MAL-2026-18241: Malicious code in workslip (PyPI)

Published Oct 23, 2026

Updated

--- -= Per source details. Do not edit below this line.=-

Source: amazon-inspector (6ed989756ad2ee3d30bbbc314bc4b4338bf246f6e3643c9fe57df33d0f2a9649) Analysis of workslip 0.1.0 on PyPI surfaced no a static rule matches and no traced behaviors indicative of supply-chain attack patterns. No install-time or import-time network I/O, no credential or filesystem harvesting, no obfuscated payloads, and no lifecycle hooks performing privileged or remote operations were observed in the shipped files.

Source: kam193 (6a509c00601b9f218feeb0cf12a7f84899efaf786edee659338d53d9888aa507) 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: 2026-10-voice-synthesis-profiles

Reasons (based on the campaign):

- other

- Downloads and executes a remote malicious script.

Affected Software

1 affected component

pip/workslip=0.1.0

Event History

Oct 23, 2026

Advisory Published

via OSV·03:53 PM

Data Sourced

via OSV·03:53 PM

DescriptionAffected Software

Frequently Asked Questions

What makes this package risky if its shipped files showed no suspicious behavior?

The package is identified as part of a coordinated loader campaign. These packages are intended to execute code obtained from a supplied URL, so the harmful payload may be delivered remotely rather than embedded in the published files.

What would an attacker need to exploit this package?

The available information indicates that exploitation depends on code being loaded from a given URL. The package itself does not contain the remote payload described by the campaign evidence.

Is there evidence that installing or importing version 0.1.0 immediately performs malicious actions?

No. Analysis of workslip 0.1.0 found no install-time or import-time network I/O, credential or filesystem harvesting, obfuscated payloads, or lifecycle hooks performing privileged or remote operations.

MAL-2026-18241: Malicious code in workslip (PyPI)

Affected Software

Event History

Frequently Asked Questions

What makes this package risky if its shipped files showed no suspicious behavior?

What would an attacker need to exploit this package?

Is there evidence that installing or importing version 0.1.0 immediately performs malicious actions?

Company

Resources

Contact

Frequently Asked Questions

What makes this package risky if its shipped files showed no suspicious behavior?

What would an attacker need to exploit this package?

Is there evidence that installing or importing version 0.1.0 immediately performs malicious actions?