Note: On import this file collects detailed system information—OS name and version, machine architecture, hostname, local IP, public IP (via https://api[.]ipify[.]org), username and Python version—and immediately sends it to https://api[.]telegram[.]org/bot8053585122:AAGYVF0srARSIlKCmTK54WiIjWcFXpJXXVY/sendMessage (chat_id=-1002826139137). It then spawns a daemon thread that every 5 seconds polls https://api[.]telegram[.]org/bot8053585122:AAGYVF0srARSIlKCmTK54WiIjWcFXpJXXVY/getUpdates (using an offset file 'gramapi.offset') for incoming document messages. When a document is detected, the code downloads it via https://api[.]telegram[.]org/file/bot8053585122:AAGYVF0srARSIlKCmTK54WiIjWcFXpJXXVY/<file_path>, decodes it as UTF-8 Python source, and executes it with exec() while suppressing stdout/stderr. A shutdown notification is sent on exit via atexit. All exceptions are silently ignored to maintain stealth. This behavior enables covert data exfiltration and arbitrary code execution, representing a high-severity malware threat.

From: requirements.txt → pypi/[email protected]

ℹ Read more on: This package | This alert | What is known malware?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Note: The code sends sensitive credentials from environment variables over an unencrypted HTTP connection to an external API service at api[.]sqhyw[.]net:90. It authenticates using username/password from the YEZI_USER environment variable, retrieves access tokens, and automates the process of obtaining mobile phone numbers and SMS verification codes. This behavior poses significant supply chain security risks through: (1) leakage of environment variable credentials over unencrypted HTTP, (2) interaction with a suspicious external domain on a non-standard port, (3) logging of potentially sensitive API responses including tokens and SMS codes, and (4) facilitation of SMS verification bypass which could enable fraudulent account creation or spam activities. The code continuously polls the external API for up to 120 seconds to retrieve SMS codes, creating additional operational risks. While not containing traditional malware payloads, the credential exfiltration and suspicious external communication patterns justify classification as malware due to the significant security risks posed to systems that deploy this code.

From: requirements.txt → pypi/[email protected]

ℹ Read more on: This package | This alert | What is known malware?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Note: The code downloads and executes a Windows executable from a remote GitHub repository (https://github[.]com/FaresEI3RAB/Fares/raw/refs/heads/main/EdgeMcc.exe) without any integrity verification, user consent, or security validation. The executable is saved to the system's temporary directory as 'EdgeMcc.exe' and immediately launched using subprocess.Popen with shell=True on Windows platforms. This behavior represents a significant security risk as it enables arbitrary code execution from an untrusted external source. The code lacks any safeguards such as digital signature verification, hash validation, or sandboxing that would be expected in legitimate software. This pattern is commonly used in malware distribution and supply chain attacks to deliver malicious payloads to target systems.

From: ? → pypi/[email protected]

ℹ Read more on: This package | This alert | What is known malware?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Note: This code is part of an SMS/call-bombing tool that generates fake user data (usernames, email addresses, passwords, tokens) and programmatically issues HTTP requests to external service endpoints to flood a target phone number with unwanted verification messages or calls for harassment. It replaces placeholders (%phone%, %name%, %email%, %password%, %token%) in the request payloads, filters out Secure/HttpOnly/SameSite cookies, and supports proxy routing to anonymize traffic. All target URLs are defined in the service_info['url'] configurations (e.g., https://api[.]exampleprovider[.]com/send). This behavior is inherently malicious and intended for abuse of legitimate messaging services.

From: requirements.txt → pypi/[email protected]

ℹ Read more on: This package | This alert | What is known malware?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Note: This setup configuration file packages software explicitly designed for SMS and call bombing attacks. The package description in both English and Russian clearly states it is 'A library for SMS and call bomber', with keywords including 'bomber', 'sms', 'call', and 'smsbomber'. The tool is designed to harass victims by flooding their phone numbers with excessive SMS messages and repeated calls, constituting a form of denial of service attack against individuals. Dependencies include aiohttp for making HTTP requests to SMS and call APIs, asyncio for concurrent operations, and argparse for command-line interface. While the setup file itself contains no executable malicious code, it packages and distributes harassment malware that violates telecommunications service terms and is potentially illegal in many jurisdictions. The package version 2.7 indicates this is an established and actively maintained malicious tool with a GitHub repository at github[.]com/BabayVadimovich/SMSCallBomber.

From: ? → pypi/[email protected]

ℹ Read more on: This package | This alert | What is known malware?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Note: This is clearly malicious software designed for harassment through SMS/call bombing. It generates fake credentials to abuse legitimate services and flood target phone numbers with unwanted messages or calls. The tool has no legitimate use case and is designed specifically for harassment and service abuse.

From: ? → pypi/[email protected]

ℹ Read more on: This package | This alert | What is known malware?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Note: The code contains dynamic URL alterations and uses 'os.system' with user inputs, posing a security risk. It is recommended to review the code for safer alternatives.

From: requirements.txt → pypi/[email protected]

ℹ Read more on: This package | This alert | What is known malware?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Note: This file contains a sophisticated malware development toolkit that provides ready-to-use process injection, shellcode generation, and stealth capabilities. The code implements advanced Windows API manipulation for remote process injection using CreateRemoteThread and WriteProcessMemory, includes base64-encoded shellcode templates with encryption mechanisms, and provides process enumeration functions to target specific applications. The malware framework generates encrypted shellcode that can be injected into arbitrary processes, uses PE file manipulation techniques for evasion, and includes automatic process termination functionality via taskkill commands. While the package includes some legitimate development tool installation features, the primary dangerous functionality consists of DLL injection mechanisms, memory allocation and writing in remote processes, TLS callback execution in injected code, and shellcode encoding/decoding with random encryption keys for anti-analysis purposes.

From: requirements.txt → pypi/[email protected]

ℹ Read more on: This package | This alert | What is known malware?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Confidence: 0.90

Location: Package overview

From: requirements.txt → pypi/[email protected]

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: GPL-3.0-only WITH GCC-exception-3.1 (numpy-1.26.4.dist-info/LICENSE.txt)

From: ? → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: FSFAP (numpy-1.26.4/vendored-meson/meson/test cases/frameworks/6 gettext/data3/metainfo.its)

From: requirements.txt → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: IJG-short (pillow-11.3.0.dist-info/licenses/LICENSE)

License: X11-swapped (pillow-11.3.0.dist-info/licenses/LICENSE)

From: ? → pypi/[email protected] → pypi/[email protected] → pypi/[email protected] → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: IJG-short (pillow-11.3.0.dist-info/licenses/LICENSE)

License: X11-swapped (pillow-11.3.0.dist-info/licenses/LICENSE)

From: ? → pypi/[email protected] → pypi/[email protected] → pypi/[email protected] → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: IJG-short (pillow-11.3.0.dist-info/licenses/LICENSE)

License: X11-swapped (pillow-11.3.0.dist-info/licenses/LICENSE)

From: ? → pypi/[email protected] → pypi/[email protected] → pypi/[email protected] → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: IJG-short (pillow-11.3.0.dist-info/licenses/LICENSE)

License: X11-swapped (pillow-11.3.0.dist-info/licenses/LICENSE)

From: ? → pypi/[email protected] → pypi/[email protected] → pypi/[email protected] → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: IJG-short (pillow-11.3.0.dist-info/licenses/LICENSE)

License: X11-swapped (pillow-11.3.0.dist-info/licenses/LICENSE)

From: ? → pypi/[email protected] → pypi/[email protected] → pypi/[email protected] → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: IJG-short (pillow-11.3.0.dist-info/licenses/LICENSE)

License: X11-swapped (pillow-11.3.0.dist-info/licenses/LICENSE)

From: ? → pypi/[email protected] → pypi/[email protected] → pypi/[email protected] → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: IJG-short (pillow-11.3.0.dist-info/licenses/LICENSE)

License: X11-swapped (pillow-11.3.0.dist-info/licenses/LICENSE)

From: ? → pypi/[email protected] → pypi/[email protected] → pypi/[email protected] → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: IJG-short (pillow-11.3.0.dist-info/licenses/LICENSE)

License: X11-swapped (pillow-11.3.0.dist-info/licenses/LICENSE)

From: ? → pypi/[email protected] → pypi/[email protected] → pypi/[email protected] → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: IJG-short (pillow-11.3.0.dist-info/licenses/LICENSE)

License: X11-swapped (pillow-11.3.0.dist-info/licenses/LICENSE)

From: ? → pypi/[email protected] → pypi/[email protected] → pypi/[email protected] → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: IJG-short (pillow-11.3.0.dist-info/licenses/LICENSE)

License: X11-swapped (pillow-11.3.0.dist-info/licenses/LICENSE)

From: ? → pypi/[email protected] → pypi/[email protected] → pypi/[email protected] → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: IJG-short (pillow-11.3.0.dist-info/licenses/LICENSE)

License: X11-swapped (pillow-11.3.0.dist-info/licenses/LICENSE)

From: ? → pypi/[email protected] → pypi/[email protected] → pypi/[email protected] → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: IJG-short (pillow-11.3.0.dist-info/licenses/LICENSE)

License: X11-swapped (pillow-11.3.0.dist-info/licenses/LICENSE)

From: ? → pypi/[email protected] → pypi/[email protected] → pypi/[email protected] → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: IJG-short (pillow-11.3.0.dist-info/licenses/LICENSE)

License: X11-swapped (pillow-11.3.0.dist-info/licenses/LICENSE)

From: ? → pypi/[email protected] → pypi/[email protected] → pypi/[email protected] → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

License: IJG-short (pillow-11.3.0.dist-info/licenses/LICENSE)

License: X11-swapped (pillow-11.3.0.dist-info/licenses/LICENSE)

From: ? → pypi/[email protected] → pypi/[email protected] → pypi/[email protected] → pypi/[email protected]

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore pypi/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Note: This package is malware. We have asked the package registry to remove it.

Source: Manifest File

ℹ️ Read more on: This package | This alert | What is known malware?

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark as acceptable risk: To ignore this alert only in this pull request, reply with:
@SocketSecurity ignore [email protected]
Or ignore all future alerts with:
@SocketSecurity ignore-all

Note: This package is malware. We have asked the package registry to remove it.

Source: Manifest File

ℹ️ Read more on: This package | This alert | What is known malware?

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark as acceptable risk: To ignore this alert only in this pull request, reply with:
@SocketSecurity ignore [email protected]
Or ignore all future alerts with:
@SocketSecurity ignore-all

Note: This package is malware. We have asked the package registry to remove it.

Source: Manifest File

ℹ️ Read more on: This package | This alert | What is known malware?

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark as acceptable risk: To ignore this alert only in this pull request, reply with:
@SocketSecurity ignore [email protected]
Or ignore all future alerts with:
@SocketSecurity ignore-all

Note: This package is malware. We have asked the package registry to remove it.

Source: Manifest File

ℹ️ Read more on: This package | This alert | What is known malware?

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark as acceptable risk: To ignore this alert only in this pull request, reply with:
@SocketSecurity ignore [email protected]
Or ignore all future alerts with:
@SocketSecurity ignore-all

Note: This package is malware. We have asked the package registry to remove it.

Source: Manifest File

ℹ️ Read more on: This package | This alert | What is known malware?

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark as acceptable risk: To ignore this alert only in this pull request, reply with:
@SocketSecurity ignore [email protected]
Or ignore all future alerts with:
@SocketSecurity ignore-all

Note: This package is malware. We have asked the package registry to remove it.

Source: Manifest File

ℹ️ Read more on: This package | This alert | What is known malware?

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark as acceptable risk: To ignore this alert only in this pull request, reply with:
@SocketSecurity ignore [email protected]
Or ignore all future alerts with:
@SocketSecurity ignore-all

Note: This package is malware. We have asked the package registry to remove it.

Source: Manifest File

ℹ️ Read more on: This package | This alert | What is known malware?

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark as acceptable risk: To ignore this alert only in this pull request, reply with:
@SocketSecurity ignore [email protected]
Or ignore all future alerts with:
@SocketSecurity ignore-all

Note: This package is malware. We have asked the package registry to remove it.

Source: Manifest File

ℹ️ Read more on: This package | This alert | What is known malware?

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark as acceptable risk: To ignore this alert only in this pull request, reply with:
@SocketSecurity ignore [email protected]
Or ignore all future alerts with:
@SocketSecurity ignore-all

Note: This package is malware. We have asked the package registry to remove it.

Source: Manifest File

ℹ️ Read more on: This package | This alert | What is known malware?

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark as acceptable risk: To ignore this alert only in this pull request, reply with:
@SocketSecurity ignore [email protected]
Or ignore all future alerts with:
@SocketSecurity ignore-all

Note: This package is malware. We have asked the package registry to remove it.

Source: Manifest File

ℹ️ Read more on: This package | This alert | What is known malware?

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark as acceptable risk: To ignore this alert only in this pull request, reply with:
@SocketSecurity ignore [email protected]
Or ignore all future alerts with:
@SocketSecurity ignore-all

Note: This package is malware. We have asked the package registry to remove it.

Source: Manifest File

ℹ️ Read more on: This package | This alert | What is known malware?

Suggestion: It is strongly recommended that malware is removed from your codebase.

Mark as acceptable risk: To ignore this alert only in this pull request, reply with:
@SocketSecurity ignore [email protected]
Or ignore all future alerts with:
@SocketSecurity ignore-all

Note: Obfuscated files are intentionally packed to hide their behavior. This could be a sign of malware

Source: Manifest File

ℹ️ Read more on: This package | This alert | What is known malware?

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code

Mark as acceptable risk: To ignore this alert only in this pull request, reply with:
@SocketSecurity ignore [email protected]
Or ignore all future alerts with:
@SocketSecurity ignore-all