Malicious Code Detected in deuro-landing-page Package - Version 5.9.9

deuro-landing-page Updated 04 Feb 2026

Summary

04/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-733: Malicious code in deuro-landing-page (npm). Affects deuro-landing-page versions 5.9.9. 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 'deuro-landing-page' package is an npm module designed for creating landing pages. It is utilized by developers to streamline the process of building web interfaces. However, version 5.9.9 has been flagged for containing malicious code that compromises user security and system integrity.

Vulnerability Detail

The vulnerability in the 'deuro-landing-page' package arises from its communication with a domain linked to malicious activities. Additionally, it executes commands that can lead to harmful behavior, potentially allowing attackers to gain unauthorized access or control over affected systems. This poses significant risks to users and their data.

How To Fix

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

npm uninstall deuro-landing-page

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, you can avoid using the 'deuro-landing-page' package altogether until a secure version is confirmed. If you must use it, consider isolating it in a controlled environment to minimize potential risks.

Conclusion

The 'deuro-landing-page' package version 5.9.9 has been identified as malicious, posing serious risks to users. It is essential to update to a secure version or implement workarounds to mitigate potential threats. Regular monitoring with tools like Vulert can help maintain security in your applications.

See every vulnerability recorded for deuro-landing-page →

Share this vulnerability

FAQ

The 'deuro-landing-page' package is an npm module used for creating landing pages in web applications.

Version 5.9.9 is considered malicious due to its communication with a harmful domain and execution of commands associated with malicious behavior.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If immediate updates are not possible, consider isolating the package in a controlled environment to reduce exposure to potential threats.

Detailed information about this vulnerability can be found in the OpenSSF Package Analysis project documentation and the package's repository.

How To Fix

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

npm uninstall deuro-landing-page

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