Which versions of bestcolorsever3 are malicious?

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

How do I remediate bestcolorsever3 if I installed it?

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

If bestcolorsever3 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is bestcolorsever3 part of a known attack campaign?

Yes — bestcolorsever3 is associated with the 2023-12-valuent 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 bestcolorsever3 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bestcolorsever3 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bestcolorsever3 across your stack and pipelines.

Malicious package

bestcolorsever3PyPI

Malicious code in bestcolorsever3 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12217

Immediate action

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

pip uninstall bestcolorsever3

What this malware does

Packages either test the malicious behaviour, or actually download and run a simple remote script during the installation.

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: 2023-12-valuent

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.
Downloads and executes a remote malicious script.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

ae08177b5187f8353a45efd2fee8e70d0d6c99b1e563f85f1cf480802f950e4d

4870c1bbc72ff9abf86bcdb025ddf4a63c361c3bd3081db4cc812f4564e6301c

3c5a60fd157533d1e47aa6b0a6642d915d9cf5cfe96449c1373ba9b742071b0b

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bestcolorsever3 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bestcolorsever3 across your stack and pipelines.
If you installed it — respond
bestcolorsever3 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 bestcolorsever3 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks bestcolorsever3 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. bestcolorsever3 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

2023-12-valuent

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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