Critical Malicious Code Vulnerability in dotyar Package

dotyar Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18675: Malicious code in dotyar (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 dotyar package is an npm library designed for specific functionalities within JavaScript applications. It is commonly utilized for its ease of integration and lightweight nature. However, recent findings have revealed that this package contains malicious code, posing a significant security risk to applications that depend on it.

Vulnerability Detail

The vulnerability in the dotyar package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code can potentially lead to unauthorized access, data breaches, or other malicious activities, making it imperative for users to address this issue promptly. The vulnerability affects all versions starting from 0, indicating that any application utilizing this package is at risk.

How To Fix

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

npm uninstall dotyar

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 replacing the functionality provided by dotyar with an alternative package that does not have known vulnerabilities. Ensure to review the security of any new package before integration.

Conclusion

The discovery of malicious code in the dotyar package poses a serious threat to applications that utilize it. Immediate action is required to mitigate risks, including uninstalling the package and seeking alternatives. Keeping abreast of updates and utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for dotyar →

Share this vulnerability

FAQ

The dotyar package is an npm library used in JavaScript applications for specific functionalities, but it has been found to contain malicious code.

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

If you are using the dotyar package, you should uninstall it immediately and look for alternative packages or wait for a patched version.

The malicious code can lead to unauthorized access, data breaches, and other security threats, compromising the integrity of your application.

Currently, there is no patch available for the dotyar package. Users are advised to uninstall the package 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 dotyar

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