Which versions of final-osint are malicious?

The following PyPI versions of final-osint are flagged malicious: 2.0.0. Treat any of these as compromised.

How do I remediate final-osint if I installed it?

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

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

Yes — final-osint is associated with the RLMA-2025-05210, 2025-09-final-osint, RLUA-2026-00325 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 final-osint across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for final-osint (version 2.0.0).

Malicious package

final-osintPyPI

Advisory published Sep 22, 2025Updated Mar 19, 2026

final-osint is a confirmed malicious PyPI package (MAL-2025-48891) that steals credentials and exfiltrates sensitive data (malicious version 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in final-osint (PyPI)

MAL-2025-48891

Immediate action

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

pip uninstall final-osint

What this malware does

Importing the module starts an infostealer exfiltrating e.g. browser data

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

Campaign: 2025-09-final-osint

Reasons (based on the campaign):

infostealer
exfiltration-browser-data
exfiltration-crypto

Malicious versions

1 flagged

2.0.0

Indicators of compromise (SHA-256)

c1f76a58390551d4469d6bc9852720e237aa2711f3d81a9bfe958526b9df00ec

284c9c0fc4357cb26d09795ec657fa920c1451b0f7826d395b341c1fddeab9e5

e4fd0b958714b427b2b2c39e7afd8134f71fae10467ce32d52cffeb74ec716c2

df6961696866e4810cf5bc45ca8f7762096bbd67ae9dd91bc865713e93720d67

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for final-osint (version 2.0.0).
If you installed it — respond
final-osint 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 final-osint 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. final-osint on PyPI has been identified as a malicious package (version 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-052102025-09-final-osintRLUA-2026-00325

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks final-osint-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