Critical Malicious Code Vulnerability in lion-second-package

lion-second-package Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190625: Malicious code in lion-second-package (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 'lion-second-package' is an npm package that serves various functionalities within JavaScript applications. It is designed to facilitate developers in managing dependencies and enhancing application performance. However, it has been identified as containing malicious code that compromises the security of any system where it is installed, making it a significant threat to users and their data.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the 'lion-second-package'. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to the package's malicious intent, which can lead to severe ramifications, including data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall lion-second-package

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

Currently, there are no effective workarounds to mitigate the risks associated with the 'lion-second-package'. The best course of action is to uninstall the package entirely.

Conclusion

The 'lion-second-package' poses a critical security risk due to the embedded malicious code it contains. Immediate action is required to uninstall the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for lion-second-package →

Share this vulnerability

FAQ

The 'lion-second-package' is an npm package used in JavaScript applications for managing dependencies and enhancing performance.

The malicious code can fully compromise your system, allowing unauthorized access to sensitive information and potentially leading to data breaches.

You should uninstall the 'lion-second-package' immediately and rotate any sensitive information stored on the affected system.

No, there is currently no patched version of the 'lion-second-package' available. The only solution is to remove the package.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json. You can check if your application is affected by visiting the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

npm uninstall lion-second-package

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