Malicious Code Vulnerability in international_magpie-notthedev Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104360: Malicious code in international_magpie-notthedev (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The international_magpie-notthedev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate development by providing reusable code. However, it has been identified as part of a malicious campaign that exploits npm's publishing features to inflate developer reputation scores through the creation of derivative packages.

Vulnerability Detail

This vulnerability originates from the package being associated with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches in their applications.

How To Fix

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

npm uninstall international_magpie-notthedev

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 international_magpie-notthedev package until a fixed version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The international_magpie-notthedev package has been identified as containing malicious code that can compromise the integrity of applications using it. It is crucial for developers to remain vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for international_magpie-notthedev →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.

Using this compromised package can lead to security breaches, as it modifies essential files and repopulates the npm registry with malicious variants.

You should remove the package and update your dependencies to ensure that you are not using any compromised code.

Yes, tools like Vulert can monitor your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues.

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

How To Fix

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

npm uninstall international_magpie-notthedev

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