Which versions of funkratov-renderkit are malicious?

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

How do I remediate funkratov-renderkit if I installed it?

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

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

Yes — funkratov-renderkit 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 funkratov-renderkit 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 funkratov-renderkit (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging funkratov-renderkit across your stack and pipelines.

Malicious package

funkratov-renderkitPyPI

funkratov-renderkit is a confirmed malicious PyPI package (MAL-2026-3213) 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 funkratov-renderkit (PyPI)

MAL-2026-3213

Immediate action

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

pip uninstall funkratov-renderkit

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)

78b5f3b4a8756df49b4a5eb41647e9dd20328da005f95869f81447355e2f7880

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 funkratov-renderkit (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging funkratov-renderkit across your stack and pipelines.
If you installed it — respond
funkratov-renderkit 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 funkratov-renderkit 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 funkratov-renderkit 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. funkratov-renderkit 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 funkratov-renderkit-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