Malicious Code Detected in archdoom Package - Security Alert

archdoom Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14791: Malicious code in archdoom (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 archdoom package is an npm library designed for [insert functionality here, e.g., game development, data processing]. It offers features such as [insert key attributes, e.g., easy integration, high performance]. However, it has been identified as containing malicious code, posing a significant security risk to users who incorporate it into their projects.

Vulnerability Detail

The vulnerability in the archdoom package stems from the inclusion of malicious code that can compromise the security of applications using this package. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or facilitate other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, 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 archdoom

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, consider using alternative packages that provide similar functionality without the associated risks. Review your project's dependencies and replace archdoom with a trusted library.

Conclusion

The discovery of malicious code in the archdoom package poses a serious threat to users. It is crucial to take immediate action by removing the package and monitoring for updates. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for archdoom →

Share this vulnerability

FAQ

archdoom is an npm package designed for [insert functionality], but it has been found to contain malicious code.

You can check your project's dependencies using tools like Vulert, which monitors vulnerabilities in real-time. Visit Vulert Scanner to assess your application without needing to sign up.

Immediately remove the archdoom package from your project and replace it with a secure alternative.

Currently, there is no patched version available. It is essential to remove the package until a secure version is released.

Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities, ensuring your application remains secure.

How To Fix

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

npm uninstall archdoom

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