Malicious Code Vulnerability in urgent_jackal-gooddev Package

urgent_jackal-gooddev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110236: Malicious code in urgent_jackal-gooddev (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 urgent_jackal-gooddev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to modify critical files and republish variants, thereby polluting the npm registry.

Vulnerability Detail

The vulnerability originates from the package being part of a token reward campaign that floods the npm registry with malicious packages. It contains scripts designed to automatically modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of trust in the ecosystem.

How To Fix

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

npm uninstall urgent_jackal-gooddev

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 remove the urgent_jackal-gooddev package from your project by executing the following command: npm uninstall urgent_jackal-gooddev. This will prevent any malicious code from executing in your environment until a secure version is available.

Conclusion

The urgent_jackal-gooddev package poses a significant security risk due to its malicious code designed to manipulate package metadata and republish itself. It is essential for developers to take immediate action to remove this package and monitor their projects for any signs of compromise. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for urgent_jackal-gooddev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to unauthorized modifications of your package.json file and the introduction of malicious code into your project, compromising its security.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without any signup at the Vulert playground.

If you have installed the urgent_jackal-gooddev package, it is crucial to uninstall it immediately and check for any unauthorized changes in your project.

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review package sources before installation.

How To Fix

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

npm uninstall urgent_jackal-gooddev

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