Critical Malicious Code Vulnerability in gkrtalpha Package

gkrtalpha Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21507: Malicious code in gkrtalpha (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 gkrtalpha package is an npm library designed for various functionalities in JavaScript applications. It is utilized by developers for its ease of integration and robust features. However, this package has been identified to contain malicious code, posing significant risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the gkrtalpha package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this vulnerability was confirmed by Amazon Inspector, highlighting the importance of addressing it promptly.

How To Fix

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

npm uninstall gkrtalpha

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

If immediate patching is not feasible, consider removing the gkrtalpha package from your project and replacing it with an alternative library that offers similar functionality without the associated risks.

Conclusion

The gkrtalpha package has been identified as containing malicious code, posing serious security risks to applications. It is essential to update the package or find alternatives to ensure the safety of your software. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for gkrtalpha →

Share this vulnerability

FAQ

gkrtalpha is an npm package used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

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

The risks include unauthorized access to sensitive data, potential data breaches, and other harmful actions that could compromise application integrity.

Yes, updating the gkrtalpha package to the latest version will help mitigate the risks associated with this vulnerability.

Consider removing the gkrtalpha package and replacing it with a safer alternative until you can implement the update.

How To Fix

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

npm uninstall gkrtalpha

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