Malicious Code Detected in retirejs Package - Vulnerability MAL-2025-6306

retirejs Updated 02 Oct 2025

Summary

24/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6306: Malicious code in retirejs (npm). Affects retirejs versions >= 0.1.2-a1. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The retirejs package is a tool designed to help developers identify and eliminate the use of vulnerable JavaScript libraries in their projects. It scans project dependencies and alerts users about known vulnerabilities, thereby enhancing the security of applications. However, a recent vulnerability has been identified that allows the package to communicate with a domain associated with malicious activity, posing a significant risk to users.

Vulnerability Detail

The vulnerability identified in the retirejs package (MAL-2025-6306) originates from version 0.1.2-a1 and allows the package to connect to a malicious domain. This could lead to data breaches, unauthorized access, or the execution of harmful code within applications utilizing this package. The technical implications are severe, as it compromises the integrity of the software and could potentially expose sensitive information to attackers.

How To Fix

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

npm uninstall retirejs

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 remove the retirejs package from your project until a secure version is available. You can do this by running: 'npm uninstall retirejs'. This will prevent any potential communication with the malicious domain until the issue is resolved.

Conclusion

The retirejs package has been found to contain a vulnerability that allows communication with a malicious domain, posing significant risks to users. It is crucial to update the package to a secure version or remove it from your project until a fix is implemented. Utilizing tools like Vulert can help monitor your application for such vulnerabilities effectively.

See every vulnerability recorded for retirejs →

Share this vulnerability

FAQ

The retirejs package is used to identify and eliminate vulnerable JavaScript libraries in projects, enhancing application security.

The vulnerability allows the package to communicate with a domain linked to malicious activities, which can compromise application security.

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

Yes, users are advised to update the retirejs package to a patched version to mitigate the risk associated with this vulnerability.

As a temporary measure, you can uninstall the retirejs package to prevent any potential risks until a secure version is available.

How To Fix

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

npm uninstall retirejs

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