Malicious Code Detected in antraege Package - Security Alert

antraege Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14609: Malicious code in antraege (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 antraege package is a Node.js library designed for managing and processing requests related to various applications. It is commonly used in web development for its ease of integration and functionality. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the antraege package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code may allow unauthorized access, data theft, or other harmful actions that could severely impact the integrity and confidentiality of user data. The malicious code was introduced in version 0 and has been confirmed by security researchers.

How To Fix

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

npm uninstall antraege

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

If immediate patching is not feasible, consider removing the antraege package from your project until a secure version is released. You can do this by running the command: 'npm uninstall antraege'. Additionally, monitor your application for any unusual activity as a precaution.

Conclusion

The discovery of malicious code in the antraege package highlights the importance of regularly monitoring and updating dependencies in software projects. It is essential to take immediate action to mitigate risks associated with this vulnerability by updating or removing the affected package.

See every vulnerability recorded for antraege →

Share this vulnerability

FAQ

The antraege package is used for managing and processing requests in Node.js applications, particularly in web development.

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 requiring any signup.

If you cannot update the package right away, consider removing it from your project and monitoring for any unusual activity.

Yes, the malicious code could potentially lead to unauthorized access and data theft, which may result in data loss or compromise.

You can find detailed information about this vulnerability on the GitHub repository of the malicious packages project or through security advisories related to the antraege package.

How To Fix

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

npm uninstall antraege

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