Critical Malicious Code Vulnerability in landingpage-service Package

landingpage-service Updated 31 Dec 2025

Summary

31/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-193005: Malicious code in landingpage-service (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The landingpage-service package is an npm module designed for creating and managing landing pages in web applications. It provides developers with tools to easily set up and customize landing pages for marketing and user engagement purposes. However, this package has been identified as containing malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the landingpage-service package. This code can compromise the security of any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that simply removing the package may not eliminate all traces of the compromise, as full control of the affected system may have been granted to an external entity.

How To Fix

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

npm uninstall landingpage-service

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 specific workarounds to mitigate the risks associated with this vulnerability other than removing the package and securing your system.

Conclusion

The landingpage-service package has been identified as containing malicious code, posing a significant security risk. Immediate action is required to remove the package and secure any compromised systems. Regular monitoring of dependencies is essential to maintain the security of your applications.

See every vulnerability recorded for landingpage-service →

Share this vulnerability

FAQ

You should immediately remove the landingpage-service package from your system and rotate any secrets or keys stored on that computer.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Keeping the package installed can lead to unauthorized access to sensitive information and potential full compromise of your system.

While removing the package is essential, you should also rotate all secrets and keys and monitor your system for any unusual activity.

While many npm packages are safe, it is crucial to regularly monitor and audit your dependencies for vulnerabilities, using tools like Vulert for real-time alerts.

How To Fix

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

npm uninstall landingpage-service

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