Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

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

    Affected
    >= 0.1.0, <= 0.1.0>= 0.1.1, <= 0.1.1
    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 (715421a3b919f086db6ad4a57d6c8d6d333b019e3a63e607be95cf3fcb7aef5d) On import, claudeopuseni/init.py invokes _boot.check(), which issues an HTTPS GET to https://thisisafalsepositive.st/cdn/v2/claudeopuseni/manifest.json, reads field 'r' as an encrypted blob (falling back to the base64-encoded _payload.PAYLOAD bundled in _payload.py when the host is unreachable), decrypts it with a ChaCha20+HMAC routine in security.unsign keyed from sha256(b'claudeopuseni.2026.channel.v1'), and passes the plaintext to builtins.exec via an attribute name assembled from chr(101,120,101,99) to hide the sink from static scanners. _boot gates detonation on the presence of a real user profile (USERPROFILE/HOME containing Documents or Downloads) and on absence of DAS_STAGED=1 or claudeopuseni_TELEMETRY=0, and caches a timestamp to suppress re-execution within 6 hours — a sandbox/CI evasion wrapper. The embedded…

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

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

Advisory: Malicious code in claudeopuseni (PyPI)
IDs: mal-2026-18299
Record: https://patchnext.com/advisories/mal-2026-18299 (revision 1, source checked 26 Oct 2026, 12:45 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 claudeopuseni: affected >= 0.1.0, <= 0.1.0; >= 0.1.1, <= 0.1.1

## Suggested inspection (read-only)
- `python -m pip show claudeopuseni`: 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 claudeopuseni.
- 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-18299 (OSV record MAL-2026-18299 lists affected ranges: PyPI claudeopuseni >=0.1.0 =0.1.1 <=0.1.1)

Commands are suggestions: review each one before running it.

Loading voting…