Which versions of meowsapi are malicious?

The following PyPI versions of meowsapi are flagged malicious: 0.2, 0.3. Treat any of these as compromised.

How do I remediate meowsapi if I installed it?

meowsapi 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 meowsapi — how do I know if it already compromised me?

If meowsapi 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 meowsapi part of a known attack campaign?

Yes — meowsapi is associated with the RLMA-2025-02579, 2025-05-rblxfando, RLUA-2026-00514 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 meowsapi 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 meowsapi (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging meowsapi across your stack and pipelines.

Malicious package

meowsapiPyPI

Malicious code in meowsapi (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-4224

Immediate action

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

pip uninstall meowsapi

What this malware does

Importing the module starts delayed downloading and starting a remote executable identified as BlankGrabber infostealer.

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

Campaign: 2025-05-rblxfando

Reasons (based on the campaign):

infostealer
Downloads and executes a remote executable.
malware
infostealer:blankgrabber

Malicious versions

2 flagged

0.20.3

Indicators of compromise (SHA-256)

41542e71d0607d431afe46d199805caacb826a5f4853d81e910107cf46763ff7

3a0c540ae9e6da2f0a28108547b1d7cd81268cc9ddd5385788703a5727f1138f

f59e6347816a732ab5ddebfd141e113bb5cca799fa8b8466f194dbff1a1e428b

404c7ac266a62146266ec23f47abf2c965915b13611fa06cc4f72428107d449c

c3109b25765e40a86b9479bbcd51d3dad1eba33c81c222a3bde9c46d0d6bec2f

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 meowsapi (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging meowsapi across your stack and pipelines.
If you installed it — respond
meowsapi 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 meowsapi 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 meowsapi 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. meowsapi on PyPI has been identified as a malicious package (versions 0.2, 0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-025792025-05-rblxfandoRLUA-2026-00514

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks meowsapi-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