Malicious Code Injection in deirdreobrien Package: npm Vulnerability Overview

deirdreobrien Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-171103: Malicious code in deirdreobrien (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The deirdreobrien package is part of the npm ecosystem, which is widely used for JavaScript package management. It is often utilized in various applications to manage dependencies and streamline development processes. However, this package has been identified as part of a malicious campaign that floods npm with harmful packages designed to manipulate developer reputation scores.

Vulnerability Detail

The vulnerability in the deirdreobrien package stems from its association with a malicious campaign that includes scripts designed to automatically generate and publish derivative packages. These scripts modify the package.json file by removing private flags, altering version numbers, and creating random package names. This behavior can lead to the pollution of the npm registry, potentially compromising the integrity of applications that depend on this package.

How To Fix

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

npm uninstall deirdreobrien

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, you can avoid using the deirdreobrien package and replace it with a trusted alternative. Always verify the integrity of packages before including them in your project.

Conclusion

The deirdreobrien package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for deirdreobrien →

Share this vulnerability

FAQ

The deirdreobrien package is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

The malicious code can lead to the pollution of the npm registry and may compromise the integrity of your application by introducing untrusted dependencies.

If you have installed the deirdreobrien package, you should uninstall it immediately using 'npm uninstall deirdreobrien' and review your project's dependencies for any other potential vulnerabilities.

You can use tools like Vulert, which monitors and alerts you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall deirdreobrien

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