Which versions of jwrincident are malicious?

The following PyPI versions of jwrincident are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate jwrincident if I installed it?

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

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

Yes — jwrincident is associated with the 2026-02-jwrincident, RLMA-2026-00446 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 jwrincident 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 jwrincident (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jwrincident across your stack and pipelines.

Malicious package

jwrincidentPyPI

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

MAL-2026-1092

Immediate action

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

pip uninstall jwrincident

What this malware does

During installation, the package starts a reverse shell

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

Campaign: 2026-02-jwrincident

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

ad20c4d6c73e649f0907879ef431132bb1566c890b55d8c5933abc09e10085fd

78e732c16fbbb5798102806ede4462a9ad40104cc38a1720c7cd935ba6851a28

c72906d78ba1d442924b92561bc44e46dfe10ec5bc71be978cad329c5d508d2c

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

Campaign

2026-02-jwrincidentRLMA-2026-00446

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter
ReversingLabs · finder

Detect & block this

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