Which versions of coredxloader are malicious?

The following PyPI versions of coredxloader are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate coredxloader if I installed it?

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

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

Is coredxloader part of a known attack campaign?

Yes — coredxloader is associated with the 2026-03-coreloader 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 coredxloader across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for coredxloader (2 malicious versions).

Malicious package

coredxloaderPyPI

Advisory published Mar 31, 2026Updated Mar 31, 2026

coredxloader is a confirmed malicious PyPI package (MAL-2026-2313) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in coredxloader (PyPI)

MAL-2026-2313

Immediate action

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

pip uninstall coredxloader

What this malware does

During importing, code starts a malicious script performing exfiltration of sensitive data and credentials from e.g. browsers and Discord clients to a remote location.

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

Campaign: 2026-03-coreloader

Reasons (based on the campaign):

infostealer
exfiltration-credentials
exfiltration-browser-data
spyware-like

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

b26408ee7735357c61e0a81e60620000999ef84eba419797b20858e5ce5b4a62

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for coredxloader (2 malicious versions).
If you installed it — respond
coredxloader 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 coredxloader 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. coredxloader on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-03-coreloader

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database