Which versions of metrok are malicious?

The following PyPI versions of metrok are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate metrok if I installed it?

Remove metrok from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — metrok is associated with the RLMA-2024-04143, RLUA-2024-08512 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 metrok across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for metrok (version 1.0.0).

Malicious package

metrokPyPI

metrok is a confirmed malicious PyPI package (MAL-2024-5361) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in metrok (PyPI)

MAL-2024-5361

Immediate action

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

pip uninstall metrok

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

673028bdd85812f200e21a455770752b05a1a545086561d3008bfad9cc04168f

00db06ad0819e981ac723a64dc713baeba47a5eb8ac924935170c2f6ae1707d5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for metrok (version 1.0.0).
If you installed it — respond
Remove metrok from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If metrok 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. metrok 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-2024-04143RLUA-2024-08512

Credits

ReversingLabs · finder

Detect & block this

O3 blocks metrok-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database