Which versions of glassbeakasr are malicious?

The following PyPI versions of glassbeakasr are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate glassbeakasr if I installed it?

glassbeakasr is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed glassbeakasr — how do I know if it already compromised me?

If glassbeakasr was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is glassbeakasr part of a known attack campaign?

Yes — glassbeakasr is associated with the 2026-10-emberlytts campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find glassbeakasr across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for glassbeakasr (version 0.1.0).

Part of a larger attack: 2026-10-emberlytts published 8 malicious packages. See the full campaign →

Malicious package

glassbeakasrPyPI

Advisory published Oct 17, 2026Updated Oct 17, 2026

glassbeakasr is a confirmed malicious PyPI package (MAL-2026-17914) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in glassbeakasr (PyPI)

MAL-2026-17914

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall glassbeakasr

What this malware does

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.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

de05a7ca1743ea6c3ceba4abc7f5452783d567b39f20007aeb57071a6d4019ed

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for glassbeakasr (version 0.1.0).
If you installed it — respond
glassbeakasr is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If glassbeakasr was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. glassbeakasr on PyPI has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-10-emberlytts

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks glassbeakasr-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database