Critical Malicious Code Vulnerability in alicov Package

alicov Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14312: Malicious code in alicov (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 alicov package is a Node.js library designed for various functionalities within JavaScript applications. It is commonly used for its ease of integration and utility in handling specific tasks. However, the package has been identified to contain malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the alicov package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code can lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action.

How To Fix

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

npm uninstall alicov

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, you can replace the alicov package with an alternative library that provides similar functionality without the associated risks. Review your project's dependencies and consider using well-maintained packages that have a good security track record.

Conclusion

The alicov package has been identified as containing malicious code, posing significant risks to applications that utilize it. Users are urged to uninstall the package and seek alternatives to ensure the security of their applications. Regular monitoring and updates are essential to maintain a secure development environment.

See every vulnerability recorded for alicov →

Share this vulnerability

FAQ

The alicov package is a Node.js library used for various functionalities in JavaScript applications.

The malicious code can lead to unauthorized access and data breaches within applications that utilize the alicov package.

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 needing to sign up.

Currently, there is no patched version available. It is recommended to uninstall the package until a secure version is released.

If immediate removal is not possible, consider implementing security measures such as code reviews and monitoring to mitigate risks until the package can be replaced.

How To Fix

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

npm uninstall alicov

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