Which versions of enchantv are malicious?

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

How do I remediate enchantv if I installed it?

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

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

Yes — enchantv 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 enchantv 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 enchantv (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 enchantv across your stack and pipelines.

Malicious package

enchantvPyPI

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

MAL-2023-8763

Immediate action

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

pip uninstall enchantv

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.

The OpenSSF Package Analysis project identified 'enchantv' @ 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)

cd0a61ade3d3a9bb9b83668fad7ee8a45f0bfe95bc9cc98270bcd15b615d875e

5ca0e3c628f824ffd462032315c24a7ba6867123fe551b90de124b344ffb5a3d

f578b605e73b68aae8c1d8a9bd3f55b810839b2bccd720bccc7f887c2e0046c8

212f492200394d484913bc8de971d20622ac4ed402a27dfd5a657e487568bd11

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 enchantv (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 enchantv across your stack and pipelines.
If you installed it — respond
enchantv 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 enchantv 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 enchantv 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. enchantv 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)
OpenSSF: Package Analysis · finder

Detect & block this

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