Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Malicious code in workcalender (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.

Add to your agent

Affected packages

  • PyPI workcalender

    Affected
    >= 17.1.0.dev0, <= 17.1.0.dev0
    Fixed in
    no fixed version recorded

Sources

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 (e6a50d22163d9cc8d0eda40abaaa32d88d5c8657ce914ba8b8c792a16cb5ca58) Analysis of the package's shipped files produced no indicators of installer-side harm: no install-time or import-time network I/O, no credential or environment scraping, no fetch-and-execute pattern, no lifecycle shell execution, no silent relay of caller data to a hardcoded destination, and no persistence or backdoor mechanism. The package appears to be a small or developmental release with no observable supply-chain attack surface.

Source: kam193 (9a336c0fa7a5b3ee5f036d678c8c0f0d549135a08d05549ee92cb11b1a7f78fa) This package contains a stub build-time helper, which in another package of the same uploader was already turned into a backdoor installation. While this package does not yet contain malicious code, it is clear it was uploaded with such intention and likely exploits dependency confusion. --- Category: MALICIOUS - The…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from osv record MAL-2026-18093

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-18093

Advisory: Malicious code in workcalender (PyPI)
IDs: mal-2026-18093
Record: https://patchnext.com/advisories/mal-2026-18093 (revision 1, source checked 30 Oct 2026, 06:25 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 workcalender: affected >= 17.1.0.dev0, <= 17.1.0.dev0

## Suggested inspection (read-only)
- `python -m pip show workcalender`: 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 workcalender.
- 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-18093 (OSV record MAL-2026-18093 lists affected ranges: PyPI workcalender >=17.1.0.dev0 <=17.1.0.dev0)

Commands are suggestions: review each one before running it.

Loading voting…