Critical Malicious Code Vulnerability in adk-github Package

adk-github Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192619: Malicious code in adk-github (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The adk-github package is an npm library that is used for various functionalities in JavaScript applications, particularly those that interact with GitHub APIs. It is designed to simplify the integration of GitHub features into applications. However, this package has been compromised, embedding malicious code that poses significant security risks to any system using it.

Vulnerability Detail

The vulnerability originates from the adk-github package, which contains embedded malicious code. This code can fully compromise any computer that has the package installed or running. The ramifications include unauthorized access to sensitive data, such as secrets and keys stored on the affected computer. Once compromised, the system may be under the control of an external entity, making it difficult to ensure complete removal of the malicious software even after uninstalling the package.

How To Fix

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

npm uninstall adk-github

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, users should avoid using the adk-github package altogether until a secure version is released. Additionally, consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The adk-github package has been identified as containing malicious code that compromises the security of any system using it. Immediate action is required to remove the package and secure sensitive data. Users are encouraged to monitor their systems and consider alternative packages until a safe version is available.

See every vulnerability recorded for adk-github →

Share this vulnerability

FAQ

Immediately uninstall the adk-github package and rotate any secrets or keys stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Failing to address this vulnerability can lead to unauthorized access to sensitive data and complete control of your system by malicious actors.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.

After removal, ensure that you rotate all secrets and keys stored on the compromised system and monitor for any unusual activity.

How To Fix

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

npm uninstall adk-github

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