Critical Malicious Code Vulnerability in changedeparment Package

changedeparment Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16783: Malicious code in changedeparment (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 changedeparment package is an npm library designed to facilitate the management of department changes within applications. It offers functionalities that allow developers to easily manipulate and track changes in departmental structures. However, this package has been found to contain malicious code that poses significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability in the changedeparment package originates from the inclusion of malicious code that can compromise the integrity of applications using this package. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the system, making it critical for developers to address this issue promptly.

How To Fix

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

npm uninstall changedeparment

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 changedeparment package from your project until a secure version is available. You can do this by executing the following command: npm uninstall changedeparment.

Conclusion

The changedeparment package has been identified to contain malicious code that poses serious security risks. It is crucial for developers to update the package to a secure version or uninstall it until a fix is available. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for changedeparment →

Share this vulnerability

FAQ

The changedeparment package is an npm library used for managing department changes in applications.

The malicious code found in the changedeparment package can lead to unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Yes, you can update the changedeparment package to a patched version to fix the vulnerability.

If an immediate update is not possible, consider uninstalling the package as a temporary measure.

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 changedeparment

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