Critical Malicious Code Vulnerability in sherpy Package

sherpy Updated 26 Sep 2026

Summary

25/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-17188: Malicious code in sherpy (PyPI). Affects sherpy versions 0.1.0 – 0.1.1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The sherpy package, available on PyPI, is designed for specific functionalities related to web scraping and automation. However, it has been identified as containing malicious code that exfiltrates sensitive files, particularly targeting Chrome extension files and Telegram data. This vulnerability poses a significant risk to users, especially those involved in cryptocurrency transactions.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the sherpy package, specifically in versions 0.1.0 and 0.1.1. When executed, this code is capable of exfiltrating sensitive information from users' systems, including files related to cryptocurrency wallets and Telegram communications. The campaign associated with this vulnerability is categorized as an infostealer, indicating its intent to gather and transmit sensitive user data without consent.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall sherpy

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, users can avoid using the sherpy package until a secure version is released. Additionally, consider using alternative packages for web scraping that do not have known vulnerabilities.

Conclusion

The sherpy package has been identified as containing malicious code that poses a significant risk to users by exfiltrating sensitive information. Immediate action is required to uninstall the affected versions and monitor for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications.

See every vulnerability recorded for sherpy →

Share this vulnerability

FAQ

The vulnerability involves malicious code that exfiltrates sensitive files from users' systems, particularly targeting cryptocurrency wallets and Telegram data.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

You should uninstall the affected versions immediately using the command 'pip uninstall sherpy' and monitor for any updates or patches.

Yes, consider using other web scraping libraries such as Beautiful Soup or Scrapy, which do not have known vulnerabilities.

Vulert monitors and alerts in real-time for open-source vulnerabilities in your software using just the Pipfile.lock, allowing you to stay informed about potential risks.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall sherpy

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback