Which versions of opentelematry-api are malicious?

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

How do I remediate opentelematry-api if I installed it?

opentelematry-api is a typosquat — you almost certainly intended a legitimately-named package. Remove opentelematry-api, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed opentelematry-api — how do I know if it already compromised me?

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

Yes — opentelematry-api is associated with the GENERIC-local-typosquatting 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 opentelematry-api across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for opentelematry-api (version 1.0.0).

Malicious package

opentelematry-apiPyPI

Advisory published Feb 12, 2026Updated Feb 19, 2026

opentelematry-api is a confirmed malicious PyPI package (MAL-2026-865) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in opentelematry-api (PyPI)

MAL-2026-865

Immediate action

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

pip uninstall opentelematry-api

What this malware does

Package is a typosquatting or dependency confusion attempt with a low-harm local-only action, like leaving a flag file.

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-local-typosquatting

Reasons (based on the campaign):

dependency-confusion
The package overrides the install command in setup.py to execute malicious code during installation.
typosquatting

The OpenSSF Package Analysis project identified 'opentelematry-api' @ 1.0.0 (pypi) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

879b0fe2de803ae267b0c1084873f040a73d2efbd5bd5639e99da836350a48f0

0952b92415445daf3837e498881c450a5025d64ae97723940ee019f3b644d01c

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for opentelematry-api (version 1.0.0).
If you installed it — respond
opentelematry-api is a typosquat — you almost certainly intended a legitimately-named package. Remove opentelematry-api, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If opentelematry-api 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. opentelematry-api 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

GENERIC-local-typosquatting

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks opentelematry-api-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