Malicious Code Detected in aliya-database Package - Security Alert

aliya-database Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14318: Malicious code in aliya-database (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 aliya-database package is an npm library designed for database management and operations. It provides developers with various functionalities to interact with databases efficiently. However, it has been identified to contain malicious code, posing a significant security risk to applications that utilize this package.

Vulnerability Detail

The vulnerability in the aliya-database package stems from the inclusion of malicious code that can compromise the security of applications using it. This code can lead to unauthorized access, data breaches, or other harmful actions within the application environment. The issue was introduced in version 0 and affects all subsequent versions.

How To Fix

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

npm uninstall aliya-database

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 workaround, consider replacing the aliya-database package with an alternative library that provides similar functionalities without the associated risks. Ensure to thoroughly review the alternative package for any known vulnerabilities.

Conclusion

The aliya-database package has been identified to contain malicious code, posing significant security risks to applications. It is essential to remove this package and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your software.

See every vulnerability recorded for aliya-database →

Share this vulnerability

FAQ

Aliya-database is an npm package used for database management, providing various functionalities for developers to interact with databases.

The specific nature of the malicious code has not been disclosed, but it poses a risk of unauthorized access and potential data breaches.

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

Currently, there is no patched version available. It is recommended to remove the aliya-database package until a secure version is released.

Remove the aliya-database package from your project immediately and consider using an alternative library for database management.

How To Fix

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

npm uninstall aliya-database

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