Which versions of glean-indexing-api-client are malicious?

The following PyPI versions of glean-indexing-api-client are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate glean-indexing-api-client if I installed it?

glean-indexing-api-client 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 glean-indexing-api-client — how do I know if it already compromised me?

If glean-indexing-api-client was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is glean-indexing-api-client part of a known attack campaign?

Yes — glean-indexing-api-client is associated with the RLMA-2025-02574, 2025-05-sl4x01, RLUA-2026-00353 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 glean-indexing-api-client across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for glean-indexing-api-client (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging glean-indexing-api-client across your stack and pipelines.

Malicious package

glean-indexing-api-clientPyPI

Malicious code in glean-indexing-api-client (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-4220

Immediate action

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

pip uninstall glean-indexing-api-client

What this malware does

Packages that seem to be created by a legit bug bounty hunter. Designed to look like created by different organisations, they contain a couple of data exfiltration (including all env variables) and potential remote code execution (though the URL seems not to serve any code).

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

Campaign: 2025-05-sl4x01

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
exfiltration-env-variables
impersonation

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

9c209056a9889f8383401fc66015ff4d79532283756582e235800905e648ec89

f24e82fe82edc6857f957ad86f6676f6f5fba7b3a3a14f7c2d7fd1623f53d0a1

c4f72985a496d7f564761c6862c160db30daaa442596d1cb609b0cc750bfad7a

a1eeadd0688f6415d094566e19fbe9e6646ae6faa66dd3b7e9beafbca54d5e29

c5afe03a831a367964dc24b6d557ce081ece12c308a6e7c1d461e7ab09d9270d

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for glean-indexing-api-client (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging glean-indexing-api-client across your stack and pipelines.
If you installed it — respond
glean-indexing-api-client 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 glean-indexing-api-client was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks glean-indexing-api-client before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. glean-indexing-api-client on PyPI has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-025742025-05-sl4x01RLUA-2026-00353

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks glean-indexing-api-client-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