Which versions of otc-metadata are malicious?

The following PyPI versions of otc-metadata are flagged malicious: 0.0.1, 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate otc-metadata if I installed it?

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

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

Yes — otc-metadata is associated with the RLMA-2025-01981, GENERIC-standard-pypi-install-pentest, RLUA-2026-00576 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 otc-metadata across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for otc-metadata (3 malicious versions).

Malicious package

otc-metadataPyPI

Advisory published Jul 26, 2024Updated Mar 19, 2026

otc-metadata is a confirmed malicious PyPI package (MAL-2025-2983) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 0.0.2, 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in otc-metadata (PyPI)

MAL-2025-2983

Immediate action

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

pip uninstall otc-metadata

What this malware does

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

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.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

3 flagged

0.0.10.0.20.0.3

Indicators of compromise (SHA-256)

3649b7c88bdf03dc0f01496593e46c9fabc384fa5b26ceca56ac8606c887bc76

b80300d06362f981eaa9f456069e50952d343b87cec26a7f6561ec0c9b1753b0

75435783250226bc7f234b0f98e4fb2b9777254a2ddbe179800f61577f6308e0

41d3cadcf9e5d6836f68301dba6e0bb945add56b12faa4bde457e449f340a542

ee74ab98c52381389e57cbc34c507179039e22cab00e08edab477675728172f3

Detection & response playbook

Credential / info stealer

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

Campaign

RLMA-2025-01981GENERIC-standard-pypi-install-pentestRLUA-2026-00576

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks otc-metadata-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