Which versions of qyrm-pipinject4 are malicious?

The following PyPI versions of qyrm-pipinject4 are flagged malicious: 1.0. Treat any of these as compromised.

How do I remediate qyrm-pipinject4 if I installed it?

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

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

Yes — qyrm-pipinject4 is associated with the 2026-03-old-qyrm-pipinject4 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 qyrm-pipinject4 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 qyrm-pipinject4 (version 1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging qyrm-pipinject4 across your stack and pipelines.

Malicious package

qyrm-pipinject4PyPI

Malicious code in qyrm-pipinject4 (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-2016

Immediate action

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

pip uninstall qyrm-pipinject4

What this malware does

During installation, the package starts a reverse shell.

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

Campaign: 2026-03-old-qyrm-pipinject4

Reasons (based on the campaign):

The package contains code to create a reverse shell, allowing an attacker to execute any commands on the victim's machine.

Malicious versions

1 flagged

1.0

Indicators of compromise (SHA-256)

9a21af6fd1f0c3069036b62cd769efe0cd35077f9141b1454397e44561c73461

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

Campaign

2026-03-old-qyrm-pipinject4

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks qyrm-pipinject4-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