Malicious code in pyalsogkert (PyPI)

pyalsogkert Updated 02 Oct 2025

Summary

26/09/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8568: Malicious code in pyalsogkert (PyPI). Affected versions are not published. 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

The pyalsogkert package is an open-source Python package available on the Python Package Index (PyPI). It is used for [provide details about the functionality and purpose of the package]. The package is vulnerable to a malicious code injection attack.

Vulnerability Detail

The vulnerability, identified as MAL-2023-8568, involves the presence of malicious code in the pyalsogkert package. The code is hidden using steganography techniques, making it difficult to detect. The attacker's payload aims to exfiltrate host information from the affected system. This can lead to unauthorized access, data breaches, and potential compromise of sensitive information.

How To Fix

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

pip uninstall pyalsogkert

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

Currently, there is no known workaround for this vulnerability. It is crucial to update the package to a secure version as soon as it becomes available.

Conclusion

The pyalsogkert package has been found to contain malicious code, posing a significant security risk to systems using this package. It is crucial for users to update to a secure version of the package as soon as it becomes available. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for pyalsogkert →

Share this vulnerability

FAQ

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your Pipfile.lock, and Vulert will analyze it for any open-source vulnerabilities, including this one.

The presence of malicious code in the pyalsogkert package can lead to unauthorized access to the affected system, data breaches, and the compromise of sensitive information. It is crucial to address this vulnerability promptly.

This vulnerability was discovered by Checkmarx, a security research company. They specialize in identifying and reporting vulnerabilities in open-source packages.

You can reach out to the maintainers of the pyalsogkert package by visiting their GitHub repository at [provide the URL of the GitHub repository].

Currently, there is no known fix for this vulnerability. It is recommended to update the package to a secure version as soon as it becomes available.

How To Fix

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

pip uninstall pyalsogkert

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