Which versions of incaperror are malicious?

The following PyPI versions of incaperror are flagged malicious: 7.0.0. Treat any of these as compromised.

How do I remediate incaperror if I installed it?

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

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

Yes — incaperror is associated with the RLMA-2025-04182, umbrella-campaign-oastify-on-install, RLUA-2026-00424 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 incaperror 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 incaperror (version 7.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging incaperror across your stack and pipelines.

Malicious package

incaperrorPyPI

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

MAL-2025-41690

Immediate action

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

pip uninstall incaperror

What this malware does

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: umbrella-campaign-oastify-on-install

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.

Malicious versions

1 flagged

7.0.0

Indicators of compromise (SHA-256)

3d0aa0a32562a00a2762cf0ff0258050e809d229acf9c09a6d634d0f292ff3b5

f5ab16d8e896a5abaaab938fb5ecd3f719951ed62d5025f1aa2f25e7336f8d00

35f38cf0821699586461d39581721c83cbeb67ee3e2001fecda0419e8b5adab5

c646c262d2896f5e7c09fa3d2ec2ef2f3f8f8a096770a5be3d004da57883897e

e0dfa35a65a6d6ca933360043c4d1c58103640ad6c97c2eca64992af42f3da26

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

Campaign

RLMA-2025-04182umbrella-campaign-oastify-on-installRLUA-2026-00424

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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