🛡️ MAL-2026-4182 — stripe-internal

⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Malicious code in stripe-internal (PyPI)

Source: kam193

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

  • The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
  • The package overrides the install command in setup.py to execute malicious code during installation.

Source: ossf-package-analysis

The OpenSSF Package Analysis project identified 'stripe-internal' @ 9.5.0 (pypi) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Affected software

MAL-2026-4182 is recorded against 1 package.

  • stripe-internal

Timeline and source

Published on 20 May 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

bad-packages.kam193.eu (Web)

Details

Severity Unknown
CVSS Score N/A
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2026-05-20
Updated 2026-08-12
Modified 2026-05-20
Fix URL N/A

Affected Packages

Software From version Fixed in
stripe-internal

Similar Threats

Free Vulnerability Check

Is your site affected by MAL-2026-4182?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against MAL-2026-4182 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.