Which versions of vielcord are malicious?

The following PyPI versions of vielcord are flagged malicious: 0.0.7.5. Treat any of these as compromised.

How do I remediate vielcord if I installed it?

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

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

Yes — vielcord is associated with the 2025-09-gtts-lts 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 vielcord 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 vielcord (version 0.0.7.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging vielcord across your stack and pipelines.

Malicious package

vielcordPyPI

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

MAL-2025-47510

Immediate action

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

pip uninstall vielcord

What this malware does

During the execution, the package silently download and runs a JAR not related to the package job. At the time of analysis, the content was corrupted

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-09-gtts-lts

Reasons (based on the campaign):

Downloads and executes a remote executable.
action-hidden-in-lib-usage

This package is designed to typosquat veilcord. When imported, it automatically decodes and executes a hidden payload.

Malicious versions

1 flagged

0.0.7.5

Indicators of compromise (SHA-256)

f35b1416b7e82dbedf8d0f943973c7f2c4af1ebd85f2a69ebd582f6c4d58f60e

a2cdbade2ade551e1b920eddd48c3586f09155ed000f3fd38ad38094b167be06

4663c6d9af6fa1feac7fd1719e4ff1a729bc8297eec7ce927a13804d475d2c8b

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

Campaign

2025-09-gtts-lts

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
Oracle using Macaron · finder

Detect & block this

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