Malicious Code Detected in 'door' Package - MAL-2025-18644

door Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18644: Malicious code in door (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 'door' package is an npm library designed for various functionalities in JavaScript applications. It is commonly used for managing access and permissions within software projects. However, this package has been identified to contain malicious code, posing a significant risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the 'door' package originates from the inclusion of malicious code that can compromise the security of applications using this library. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue is present in all versions starting from the initial release, making it critical for users to take immediate action.

How To Fix

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

npm uninstall door

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, consider removing the 'door' package from your project until a secure version is released. You can do this by running: 'npm uninstall door'. This will help mitigate the risk of exposure to the malicious code.

Conclusion

The discovery of malicious code in the 'door' package highlights the importance of maintaining vigilance in software dependencies. Users must take immediate action to mitigate risks by updating or removing the affected package. Regular monitoring and utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

See every vulnerability recorded for door →

Share this vulnerability

FAQ

The 'door' package is an npm library used for managing access and permissions in JavaScript applications.

The malicious code can potentially allow unauthorized access and lead to data breaches in applications that utilize the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner without any signup.

As of now, a patched version is not available. Users are advised to monitor the package repository for updates.

If removal is not an option, ensure to implement strict access controls and monitor your application for any suspicious activity until a secure version is released.

How To Fix

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

npm uninstall door

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