Critical Malicious Code Vulnerability in deadwiki Package

deadwiki Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18121: Malicious code in deadwiki (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 deadwiki package is an npm library designed for managing and interacting with wiki-style content. It offers functionalities such as content creation, editing, and retrieval, making it a popular choice for developers looking to implement wiki features in their applications. However, the package has been identified to contain malicious code, posing significant security risks to users and their applications.

Vulnerability Detail

The vulnerability in the deadwiki package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This malicious code can lead to unauthorized access, data breaches, or even complete system takeover, depending on the context in which the package is used. The issue affects all versions starting from 0, making it critical for users to take immediate action to protect their applications.

How To Fix

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

npm uninstall deadwiki

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, users can remove the deadwiki package from their project until a secure version is released. This can be done by executing the following command: 'npm uninstall deadwiki'. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The deadwiki package has been identified to contain malicious code that poses significant security risks to applications. Users are urged to update the package to a secure version or remove it until a fix is available. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.

See every vulnerability recorded for deadwiki →

Share this vulnerability

FAQ

The deadwiki package is an npm library for managing wiki-style content, allowing developers to create and edit wiki pages within their applications.

The malicious code can lead to unauthorized access and potential data breaches, posing serious security threats to applications using the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By simply analyzing your package-lock.json file, you can determine if your application is affected.

Yes, Vulert allows you to monitor vulnerabilities using just your package-lock.json file, providing alerts without requiring access to the code or installation.

If immediate updates are not possible, consider removing the package temporarily and exploring alternative libraries that offer similar functionalities without the security risks.

How To Fix

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

npm uninstall deadwiki

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