Critical Malicious Code Vulnerability in responsible-ai Package

responsible-ai Updated 13 Feb 2026

Summary

13/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-890: Malicious code in responsible-ai (npm). Affected versions are not published. 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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The responsible-ai package is an npm library designed to facilitate the development of responsible artificial intelligence applications. It provides tools and frameworks for implementing ethical AI practices. However, this package has been compromised, leading to severe security risks for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the responsible-ai package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that even after removal of the package, there is no guarantee that all traces of the malware will be eliminated, potentially leaving systems vulnerable to further attacks.

How To Fix

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

npm uninstall responsible-ai

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

Currently, there are no effective workarounds to mitigate the risks posed by the responsible-ai package. The only safe course of action is to remove the package entirely and replace it with a secure alternative.

Conclusion

The responsible-ai package has been compromised with malicious code, posing significant security risks to any system that utilizes it. Immediate action is required to uninstall the package and secure sensitive information. Users are encouraged to seek alternative solutions and utilize tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for responsible-ai →

Share this vulnerability

FAQ

Immediately uninstall the package using 'npm uninstall responsible-ai' and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Keeping the package installed can lead to unauthorized access to your system, exposing sensitive data and potentially allowing further malicious activities.

Yes, consider exploring other npm packages that focus on responsible AI practices but do not have known vulnerabilities.

While removing the package is essential, there is no guarantee that all malicious software will be removed. It is crucial to rotate all secrets and keys stored on the affected system.

How To Fix

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

npm uninstall responsible-ai

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