# MAL-2026-17914: Malicious code in glassbeakasr (PyPI)


- **Type:** Malicious package
- **Package:** `glassbeakasr` (PyPI)
- **Published:** 17 Oct 2026

## What is MAL-2026-17914?

MAL-2026-17914 is a malicious package in glassbeakasr, published on 17 Oct 2026. 

### Official description

The package exposes a run(profile, url, **kwargs) function that fetches a caller-supplied URL and executes the response body as Python via exec(compile(src, url, 'exec'), mod.__dict__). The URL is not hardcoded, there are no install-time or import-time hooks, no top-level network I/O, and no reads of installer secrets or environment variables. The remote-code execution surface is only reached if a caller explicitly invokes run() with a URL they chose. This is an advertised dynamic-loader API rather than a covert dropper, but the design pattern is inherently hazardous: any caller passing an attacker-influenced URL would execute arbitrary Python in-process with no integrity or signature check.

The package belongs to a series of packages falsely advertising 'audio-analysis profiles' loader. In fact, the only purpose is to execute remote code, but the URL is not embedded in the package. It is likely a continuation of the coin-mining campaign 2026-10-voxeval which used similar wording.

---

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

Campaign: 2026-10-emberlytts

Reasons (based on the campaign):

 - other

 - Downloads and executes a remote malicious script.

## What should I do about MAL-2026-17914?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-17914 is a malicious package: glassbeakasr (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-17914/ (Markdown: https://insights.sbomify.com/MAL-2026-17914/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-17914

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-17914/
Summaries are generated and may contain mistakes; the official description above is the record.