Malicious Code Vulnerability in qwery-core Package

qwery-core Updated 03 Mar 2026

Summary

03/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1226: Malicious code in qwery-core (PyPI). Affects qwery-core versions 1.0.0 – 1.0.7. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

qwery-core is a package available on PyPI that is designed to provide utility functions for querying and manipulating data structures. However, it has been compromised, leading to the introduction of malicious code that can download and execute harmful scripts. This vulnerability poses significant risks to users who may unknowingly install the compromised package.

Vulnerability Detail

The qwery-core package contains obfuscated code that acts as a downloader for encrypted malicious scripts. This code is compiled into a native binary, requiring a remote URL to execute the malicious payload. The vulnerability originated from a malicious actor impersonating a legitimate npm library, which raises concerns about the integrity of packages in the ecosystem. Users who install this package may inadvertently expose their systems to infostealers and other malicious activities.

How To Fix

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

pip uninstall qwery-core

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 qwery-core package altogether until a secure version is available. Additionally, consider using alternative libraries that provide similar functionality without the associated risks.

Conclusion

The qwery-core package has been identified as containing malicious code that poses significant risks to users. It is essential to take immediate action by uninstalling the affected versions and monitoring for updates. Utilizing tools like Vulert can help in real-time monitoring for vulnerabilities in open-source software.

See every vulnerability recorded for qwery-core →

Share this vulnerability

FAQ

Versions 1.0.0 to 1.0.7 of qwery-core are affected by this vulnerability.

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

If you have installed qwery-core, it is recommended to uninstall it immediately and monitor for any updates regarding a secure version.

Using the compromised package may lead to the execution of malicious scripts, potentially resulting in data theft, system compromise, or other harmful actions.

More information can be found in the official GitHub repository for malicious packages or by following updates from security analysts.

How To Fix

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

pip uninstall qwery-core

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