Critical Malicious Code Vulnerability in amdocs-core Package

amdocs-core Updated 09 Jan 2026

Summary

09/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-171: Malicious code in amdocs-core (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The amdocs-core package is a library used in various Node.js applications, providing essential functionalities for developers. However, it has been identified as containing malicious code that compromises the security of any system where it is installed. This vulnerability poses significant risks, including unauthorized access to sensitive data and potential control over the affected systems.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the amdocs-core package. This code can lead to a complete compromise of any computer running the package, allowing attackers to access secrets and keys stored on the system. The implications are severe, as the malicious code may not be fully removed even after uninstalling the package, leaving systems vulnerable to further attacks.

How To Fix

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

npm uninstall amdocs-core

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, it is recommended to uninstall the amdocs-core package using the command: npm uninstall amdocs-core. However, be aware that this may not eliminate all traces of the malicious code, and further security measures should be taken.

Conclusion

The amdocs-core package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to uninstall the package and secure any sensitive information. Users should remain vigilant and monitor for updates regarding this vulnerability.

See every vulnerability recorded for amdocs-core →

Share this vulnerability

FAQ

Immediately uninstall the amdocs-core package and rotate any sensitive keys or secrets stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

Currently, there is no patch available. The best course of action is to uninstall the package and monitor for any updates from the maintainers.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, complete control of your system by attackers, and potential data breaches.

It is advisable to avoid using the amdocs-core package until a verified, secure version is released by the maintainers.

How To Fix

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

npm uninstall amdocs-core

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