Malicious Code Detected in fourlic Package - Security Alert

fourlic Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20824: Malicious code in fourlic (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The fourlic package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of use and integration capabilities. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that rely on it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the fourlic package. This code can potentially compromise the integrity of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. 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 fourlic

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 measure, consider removing the fourlic package from your project until a secure version is released. You can do this by executing: 'npm uninstall fourlic'. This will prevent any potential exploitation of the malicious code while you seek alternatives.

Conclusion

The discovery of malicious code in the fourlic package highlights the importance of regularly monitoring and updating dependencies in software projects. Users must take immediate action to secure their applications by updating or removing the affected package.

See every vulnerability recorded for fourlic →

Share this vulnerability

FAQ

The fourlic package is an npm library used in JavaScript applications for various functionalities. However, it has been found to contain malicious code.

The malicious code was identified by security researchers from Amazon Inspector, who reported the vulnerability to the community.

Using the fourlic package can lead to unauthorized access to your application, data breaches, and other security threats due to the embedded malicious code.

Users are advised to check for a patched version of the fourlic package and update it immediately to mitigate the risk.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application against known vulnerabilities using the Vulert playground.

How To Fix

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

npm uninstall fourlic

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