What does the flamepro malware do?

Installing the package starts downloading and installing an Infostealer Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers. Campaign: 2024-12-graphicsx Reasons (based on the campaign): - The package overrides the install command in setup.py to execute malicious code during installation. - obfuscation - Downloads and executes a remote executable. - infostealer - exfiltration-browser-data

Which versions of flamepro are malicious?

The following PyPI versions of flamepro are flagged malicious: 0.1. Treat any of these as compromised.

How do I remediate flamepro if I installed it?

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

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

Yes — flamepro is associated with the RLMA-2025-01962, 2024-12-graphicsx, RLUA-2026-00327 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 flamepro 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 flamepro (version 0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging flamepro across your stack and pipelines.

Malicious package

flameproPyPI

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

MAL-2025-2964

Immediate action

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

pip uninstall flamepro

What this malware does

Installing the package starts downloading and installing an Infostealer

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

Campaign: 2024-12-graphicsx

Reasons (based on the campaign):

The package overrides the install command in setup.py to execute malicious code during installation.
obfuscation
Downloads and executes a remote executable.
infostealer
exfiltration-browser-data

Malicious versions

1 flagged

0.1

Indicators of compromise (SHA-256)

1a33bd4f6faf79a7cee27e23e879322b6222cced39ffaaa3f0731cf639f46392

7ec2eaaeb4b4bef9c2011136563e49c6a94431d9aa6d258ab9d5914aadb02dab

53c4ea20a42b8ba4c81e1625a540dbe1eff5fde676d280fb1b1a53d04b7ef069

d4374cec641c8ab5d2d18861f7091d55fac7901e342ce52b0e37e6fd9c4183dd

2d1555cab0858b9fb1344cb697902fbb5227fd8a2bdf38dcbf8538b69b331652

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

Campaign

RLMA-2025-019622024-12-graphicsxRLUA-2026-00327

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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