Which versions of renderkitcore are malicious?

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

How do I remediate renderkitcore if I installed it?

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

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

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

Search your lockfiles and build artifacts for renderkitcore (version 0.1.0).

Malicious package

renderkitcorePyPI

Advisory published May 1, 2026Updated May 1, 2026

renderkitcore is a confirmed malicious PyPI package (MAL-2026-3214) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in renderkitcore (PyPI)

MAL-2026-3214

Immediate action

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

pip uninstall renderkitcore

What this malware does

Package is prepared to exfiltrate .log and .txt files to the target already associated with exfiltrating sensitive data.

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

Campaign: 2026-04-renderctx

Reasons (based on the campaign):

backdoor
files-exfiltration
crypto-related
The malicious code is intentionally included in a dependency of the package

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

a66bf58bff553ec613604164eb60adcb89fcde468491b746838a6e2c18b0e3a0

Detection & response playbook

Credential / info stealer

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

Campaign

2026-04-renderctx

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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