Which versions of x2vml-gml are malicious?

The following PyPI versions of x2vml-gml are flagged malicious: 99.7. Treat any of these as compromised.

How do I remediate x2vml-gml if I installed it?

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

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

Yes — x2vml-gml is associated with the 2024-11-byted-dast 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 x2vml-gml 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 x2vml-gml (version 99.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging x2vml-gml across your stack and pipelines.

Malicious package

x2vml-gmlPyPI

Malicious code in x2vml-gml (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-10363

Immediate action

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

pip uninstall x2vml-gml

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

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: 2024-11-byted-dast

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.
typosquatting
dependency-confusion

The OpenSSF Package Analysis project identified 'x2vml-gml' @ 99.7 (pypi) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.7

Indicators of compromise (SHA-256)

cb1d2f963982b051c70a7149ccd500d8e39c022b77ea0da9a8bfeb10959bf8e8

92b440ba96c48a325519085edfc8c7b4f5a5438a9a9a51f65dd377ca2bb88c89

c0a24139221a012c1dcb193331f49469571c2400d49c53489603dd68b26698e6

e2876f88cd0afb5bc23f986e72bc49ece9bf15e367344924060f1bb76a99ddff

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 x2vml-gml (version 99.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging x2vml-gml across your stack and pipelines.
If you installed it — respond
x2vml-gml 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 x2vml-gml 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 x2vml-gml 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. x2vml-gml on PyPI has been identified as a malicious package (version 99.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-11-byted-dast

References

bad-packages.kam193.eu

Credits

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

Detect & block this

O3 blocks x2vml-gml-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