Malicious Code Detected in Changed-Services Package (npm)

changed-services Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-16782: Malicious code in changed-services (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 'changed-services' package is an npm module designed to facilitate the management of service changes in applications. It offers features such as tracking service updates and automating deployment processes. However, it has been identified as containing malicious code, posing a significant risk to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in the 'changed-services' package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue originated from the package's codebase, which was found to be intentionally modified to include harmful functionalities.

How To Fix

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

npm uninstall changed-services

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 measure, consider using alternative packages that provide similar functionalities without the associated risks. Review your project's dependencies and replace 'changed-services' with a trusted package until a secure version is released.

Conclusion

The 'changed-services' package has been identified as containing malicious code, posing a serious risk to users. It is crucial to remove this package from your projects and monitor for updates or alternatives. Utilizing tools like Vulert can help in identifying and managing such vulnerabilities effectively.

See every vulnerability recorded for changed-services →

Share this vulnerability

FAQ

The malicious code is designed to compromise application security, potentially allowing unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without needing to sign up.

Immediately remove the 'changed-services' package and look for alternative solutions. Monitor for any updates regarding a patched version.

Regularly audit your dependencies and utilize tools like Vulert to monitor for vulnerabilities in real-time.

Detailed information can be found on the GitHub repository or vulnerability databases that track open-source vulnerabilities.

How To Fix

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

npm uninstall changed-services

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