Critical Malicious Code Vulnerability in jwrincident Package

jwrincident Updated 01 Mar 2026

Summary

28/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1092: Malicious code in jwrincident (PyPI). Affects jwrincident versions 1.0.0 – 1.0.1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The jwrincident package, available on PyPI, is designed for incident reporting and management within Python applications. It allows developers to integrate incident handling features into their software. However, this package has been found to contain malicious code that poses a significant security risk to users.

Vulnerability Detail

The vulnerability originates from a malicious code snippet embedded in the jwrincident package, specifically in versions 1.0.0 and 1.0.1. During installation, this code initiates a reverse shell, enabling attackers to execute arbitrary commands on the victim's machine. This poses severe risks, including unauthorized access to sensitive data and complete system compromise.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall jwrincident

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users can avoid using the jwrincident package until a secure version is released. Additionally, consider using alternative packages for incident management that do not have known vulnerabilities.

Conclusion

The jwrincident package has a critical vulnerability that allows for malicious code execution. Users must take immediate action to uninstall the affected versions and monitor for updates. Utilizing tools like Vulert can help in identifying and managing vulnerabilities in your software dependencies.

See every vulnerability recorded for jwrincident →

Share this vulnerability

FAQ

The jwrincident package is a Python library designed for incident reporting and management in applications.

The vulnerability allows attackers to execute arbitrary commands on your machine, potentially leading to data theft or system compromise.

Uninstall the package immediately and monitor for any updates or patches that address the vulnerability.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Yes, Vulert offers real-time monitoring and alerts for open-source vulnerabilities using just the Pipfile.lock, ensuring your software remains secure.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall jwrincident

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback