Malicious Code Detected in encrypt-layout-helper Package

encrypt-layout-helper Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-19644: Malicious code in encrypt-layout-helper (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The encrypt-layout-helper package is a utility designed for managing layout encryption in web applications. It provides developers with tools to secure sensitive layout data. However, the package has been found to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the encrypt-layout-helper package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead 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 address this vulnerability promptly.

How To Fix

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

npm uninstall encrypt-layout-helper

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 workaround, you can avoid using the encrypt-layout-helper package altogether and seek alternative packages that provide similar functionality without the associated risks.

Conclusion

The encrypt-layout-helper package has been identified as containing malicious code, posing a significant risk to applications. It is crucial for developers to remove this package and seek alternatives to ensure the security of their applications.

See every vulnerability recorded for encrypt-layout-helper →

Share this vulnerability

FAQ

The encrypt-layout-helper package is a utility for managing layout encryption in web applications, aimed at securing sensitive layout data.

The malicious code can lead to unauthorized access and potential data breaches, compromising the security of applications that use the package.

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

Currently, there is no patched version available. It is recommended to remove the package until a secure alternative is found.

Remove the encrypt-layout-helper package immediately and consider using alternative packages that do not have known vulnerabilities.

How To Fix

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

npm uninstall encrypt-layout-helper

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