MAL-2026-19188: Malicious code in phoneliasr (PyPI)

Published Nov 12, 2026
·
Updated

--- -= Per source details. Do not edit below this line.=-

Source: kam193 (0fb66d50cba21c857c53f0336e328c0d81eb1aba12a77b17e29f3e818302c1f7) This campaign consists of similar loader packages, which provide executing code from a given URL. While they do not contain the malicious payload and the usage remains unknown, they are clearly a coordinated campaign to place multiple deceptive ways to load malicious code.

---

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-10-voice-synthesis-profiles

Reasons (based on the campaign):

- other

- Downloads and executes a remote malicious script.

Affected Software

1 affected component
pip/phoneliasr=0.1.0

Event History

Nov 12, 2026
Advisory Published
via OSV·08:49 PM
Data Sourced
via OSV·08:49 PM
DescriptionAffected Software

Frequently Asked Questions

1

What does an attacker need in order to exploit this package?

The package is described as a loader that executes code from a supplied URL. Exploitation depends on the package being installed and invoked with, or otherwise receiving, a URL pointing to attacker-controlled code.

2

Does the package need to contain the final malicious payload to be dangerous?

No. The reported behavior downloads and executes a remote script, so the payload can be hosted separately and changed without republishing the package.

3

Who is most likely exposed?

Environments that installed or executed the phoneliasr PyPI package are potentially exposed, particularly where it was used to load code from external URLs. The available data does not state whether any specific default configuration triggers this behavior.

4

What should be checked during triage?

Check dependency and package-install records for phoneliasr, then review execution history for the package and any URLs it was given or contacted. Investigate downloaded scripts and their resulting process, file, and network activity.

5

What can be done if removal cannot happen immediately?

Prevent the package from reaching external URLs and do not invoke it with untrusted or unknown URLs. This reduces the reported download-and-execute behavior while the package is removed or the environment is investigated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203