What does the vibrant malware do?

The OpenSSF Package Analysis project identified 'vibrant' @ 1.0.0 (pypi) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of vibrant are malicious?

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

How do I remediate vibrant if I installed it?

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

If vibrant 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.

How do I find vibrant across my projects, lockfiles, and CI pipelines?

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

Malicious package

vibrantPyPI

vibrant is a confirmed malicious PyPI package (MAL-2023-8770) 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 vibrant (PyPI)

MAL-2023-8770

Immediate action

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

pip uninstall vibrant

What this malware does

The OpenSSF Package Analysis project identified 'vibrant' @ 1.0.0 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

aaa7491953b666535f724cc8b060802509b09ef8e13b4f3c5ebaa6a0554e4c17

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for vibrant (version 1.0.0).
If you installed it — respond
Remove vibrant 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 vibrant 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. vibrant 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.

Credits

OpenSSF: Package Analysis · finder

Detect & block this

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