Critical Malicious Code Vulnerability in api-services Package

api-services Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14645: Malicious code in api-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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The api-services package is a widely used npm library that provides various APIs for service integration in web applications. It is designed to streamline the development process by offering pre-built functionalities. However, it has been identified to contain malicious code that poses significant security risks to applications utilizing this package.

Vulnerability Detail

The vulnerability in the api-services package stems from the inclusion of malicious code, which can compromise the integrity and security of applications that depend on it. This code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The malicious nature of this vulnerability was discovered by Amazon Inspector, highlighting the importance of vigilance in package management.

How To Fix

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

npm uninstall api-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, you can remove the api-services package from your project until a secure version is available. You can do this by executing: npm uninstall api-services. Consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The api-services package has been found to contain malicious code, posing serious security risks to applications that utilize it. It is crucial to update to a patched version or remove the package until a secure alternative is found. Regular monitoring and vulnerability checks are essential for maintaining application security.

See every vulnerability recorded for api-services →

Share this vulnerability

FAQ

The api-services package is an npm library that offers various APIs for service integration in web applications, aimed at simplifying development.

The malicious code was identified by Amazon Inspector, a security tool that scans for vulnerabilities in open-source packages.

Using the compromised package can lead to unauthorized access, data breaches, and exploitation of your application, putting user data at risk.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If immediate updates are not possible, consider removing the package temporarily and using alternative solutions until a secure version is available.

How To Fix

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

npm uninstall api-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