Critical Vulnerability in alico Package

alico Updated 02 Oct 2025

Summary

03/09/2020
CRITICAL
No i
Critical
9.8

GHSA-jfx5-7mr2-g8hg: Malicious Package in alico. Affects alico versions >= 0.0.0. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The alico package is an npm package used for [provide brief description of the package's functionality and key attributes]. It is vulnerable to a critical security issue that affects all versions of the package. The vulnerability allows malicious code to be executed on the system, compromising its security and potentially leading to unauthorized access and data breaches.

Vulnerability Detail

The vulnerability in the alico package involves the presence of malicious code that uploads system information to a remote server, downloads a file, and executes it. This can result in a complete compromise of the affected computer. It is recommended to consider any computer with this package installed or running as fully compromised. Immediate action should be taken to rotate all secrets and keys stored on the compromised computer from a different, secure computer. Although removing the package is advised, it may not guarantee the removal of all malicious software that may have been installed as a result of its installation.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to follow the recommended steps to fix the issue and mitigate any potential damage.

Conclusion

The alico package is vulnerable to a critical security issue that allows for the execution of malicious code on the system. It is crucial to take immediate action to fix the vulnerability, rotate compromised secrets and keys, and conduct a thorough security audit. Additional security measures should be implemented to prevent future attacks. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for alico →

Share this vulnerability

FAQ

The impact of this vulnerability can be severe, as it allows for unauthorized access to the affected system and potential data breaches. All secrets and keys stored on the compromised computer should be considered compromised and rotated immediately.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities using package-lock.json without requiring access to the code or installation.

Removing the alico package is advised, but there is no guarantee that it will remove all malicious software resulting from its installation. A thorough security audit and additional measures should be implemented to ensure the system's integrity.

If your system is compromised, follow the recommended steps to fix the vulnerability, including rotating all secrets and keys stored on the compromised system from a secure computer. Additionally, conduct a thorough security audit and implement additional security measures to prevent future attacks.

To prevent future attacks, it is essential to implement additional security measures such as network segmentation, access controls, and regular security audits. Stay updated with security advisories and promptly apply patches and updates to mitigate known vulnerabilities.

Related vulnerabilities

Recent vulnerabilities recorded for alico.

How To Fix

No fixed version is published for this vulnerability.

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