Malicious code in dependdency (npm) - MAL-2024-2078

dependdency Updated 02 Oct 2025

Summary

25/06/2024
CRITICAL
No i
Critical
Not published

MAL-2024-2078: Malicious code in dependdency (npm). Affects dependdency versions 1.0.0. 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 package under scrutiny is dependdency, an npm package. It is used as a dependency in various projects and provides functionality related to dependency management. The package is vulnerable to a specific issue identified as MAL-2024-2078.

Vulnerability Detail

The vulnerability identified as MAL-2024-2078 involves the presence of malicious code in the dependdency package. This code can potentially be exploited by attackers to execute arbitrary commands, compromise the security of the system, or gain unauthorized access. The origin of this vulnerability is a specific version (1.0.0) of the package. It is crucial to address this vulnerability promptly to prevent any potential harm to the affected systems.

How To Fix

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

npm uninstall dependdency

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 workaround, if updating the package is not immediately feasible, it is recommended to remove the dependdency package from the project's dependencies and find an alternative package that provides similar functionality. This will help mitigate the risk associated with the vulnerability.

Conclusion

The dependdency package has been identified with a vulnerability (MAL-2024-2078) that involves the presence of malicious code. It is crucial to update the package to a secure version or find an alternative package to mitigate the risk associated with this vulnerability. By staying informed about vulnerabilities and taking prompt actions, you can ensure the security of your applications.

See every vulnerability recorded for dependdency →

Share this vulnerability

FAQ

This vulnerability can potentially allow attackers to execute arbitrary commands, compromise the system's security, or gain unauthorized access.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert uses package-lock.json to monitor and alert in real-time for open-source vulnerabilities, providing a convenient way to assess the impact on your application.

Yes, it is recommended to update the dependdency package to a secure version that does not contain the malicious code. The maintainers of the package have likely released a patched version to address this issue.

If updating the package is not immediately feasible, it is advised to remove the dependdency package from your project's dependencies and find an alternative package that provides similar functionality. This will help mitigate the risk associated with the vulnerability.

Vulert is a platform that provides real-time monitoring and alerts for open-source vulnerabilities in software. By using Vulert, you can stay informed about vulnerabilities and take necessary actions to secure your applications.

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 dependdency

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