Critical Malicious Code Vulnerability in datanhac Package

datanhac Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18002: Malicious code in datanhac (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 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 datanhac package is a Node.js library commonly used in various applications for data handling and manipulation. It is designed to facilitate efficient data processing tasks. However, this package has been identified as containing malicious code, which poses significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in the datanhac package originates from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this code was discovered by Amazon Inspector, highlighting the importance of scrutinizing third-party packages for security flaws.

How To Fix

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

npm uninstall datanhac

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 may consider removing the datanhac package from your project until a secure version is released. You can do this by executing: npm uninstall datanhac.

Conclusion

The datanhac package has been identified as containing malicious code, posing significant risks to applications that utilize it. It is crucial to update or remove this package to safeguard your application from potential threats. Regular monitoring and vulnerability assessments are essential to maintain software security.

See every vulnerability recorded for datanhac →

Share this vulnerability

FAQ

The datanhac package is a Node.js library used for data handling and manipulation in various applications.

The malicious code can lead to unauthorized access and potential data breaches in applications that utilize the datanhac package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without any signup.

If an immediate update is not possible, consider removing the datanhac package as a temporary measure until a secure version is available.

The vulnerability was discovered by Amazon Inspector, a tool designed to identify security issues in software packages.

How To Fix

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

npm uninstall datanhac

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