Malicious Code Detected in derhatano Package - MAL-2025-18301

derhatano Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18301: Malicious code in derhatano (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 derhatano package is an npm library that serves various functionalities within JavaScript applications. It is designed to facilitate specific tasks, but it has been found to contain malicious code, posing a significant risk to users and their applications. The presence of such code can lead to unauthorized access, data breaches, and other security issues.

Vulnerability Detail

The vulnerability in the derhatano package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code can lead to severe ramifications, including unauthorized data access, data manipulation, and potential exploitation of the system. The malicious nature of this vulnerability makes it critical for users to address it immediately to safeguard their applications.

How To Fix

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

npm uninstall derhatano

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 workaround, users can temporarily disable the functionalities that rely on the derhatano package until a secure solution is implemented. This can be done by commenting out the relevant code sections in your application that utilize this package.

Conclusion

The derhatano package has been identified to contain malicious code, posing a serious threat to users. It is crucial to remove this package and seek alternatives to ensure the security of your applications. Regular monitoring for vulnerabilities using tools like Vulert can help maintain application security.

See every vulnerability recorded for derhatano →

Share this vulnerability

FAQ

The derhatano package is an npm library used in JavaScript applications for various functionalities.

The malicious code in derhatano can lead to unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application with the Vulert playground at Vulert Scanner.

You should remove the derhatano package from your project and replace it with a secure alternative.

Currently, there is no patched version available. It is recommended to look for alternative packages.

How To Fix

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

npm uninstall derhatano

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