Critical Malicious Code Vulnerability in portal-lise Package

portal-lise Updated 30 Dec 2025

Summary

30/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192970: Malicious code in portal-lise (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 portal-lise package is an npm library designed for managing various functionalities within web applications. It is commonly used for its ease of integration and flexibility. However, this package has been identified as containing malicious code, posing significant security risks to systems that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the portal-lise 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 implications of this vulnerability are severe, as it may lead to 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 portal-lise

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

There are no effective workarounds for this vulnerability. The best course of action is to remove the package entirely and secure your system.

Conclusion

The portal-lise package has been identified as containing malicious code that poses a significant risk to any system using it. Immediate removal of the package and rotation of sensitive information is necessary to mitigate the potential damage. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for portal-lise →

Share this vulnerability

FAQ

You should remove the portal-lise package immediately and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your systems.

Unfortunately, there are no effective mitigations available. The only safe option is to remove the package.

While removing the package is essential, it does not guarantee complete security. You should also rotate all secrets and keys and monitor your system for any signs of compromise.

How To Fix

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

npm uninstall portal-lise

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