Malicious Code Detected in js-3ha3 Package - Security Alert

js-3ha3 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-23913: Malicious code in js-3ha3 (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 js-3ha3 package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for its ease of integration and functionality. However, this package has been identified to contain malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the js-3ha3 package originates from the inclusion of malicious code that can compromise the integrity of applications using this package. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the application environment. The issue is particularly concerning as it affects all versions of the package starting from its introduction, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall js-3ha3

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 using an alternative package that provides similar functionality without the associated risks. Review your package-lock.json file to identify dependencies that may be affected and replace the js-3ha3 package with a safer alternative.

Conclusion

The discovery of malicious code in the js-3ha3 package highlights the importance of regularly auditing dependencies in your applications. Immediate action is required to mitigate risks associated with this vulnerability. By removing the affected package and monitoring for updates, you can help secure your application.

See every vulnerability recorded for js-3ha3 →

Share this vulnerability

FAQ

The js-3ha3 package is an npm library used in JavaScript applications for various functionalities.

The malicious code can lead to unauthorized access and data breaches within applications that utilize this package.

You can use Vulert to monitor and alert for vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If immediate removal is not possible, consider using an alternative package that offers similar functionality while ensuring security.

Utilize tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time, ensuring you are alerted to any issues.

Related vulnerabilities

Recent vulnerabilities recorded for js-3ha3.

How To Fix

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

npm uninstall js-3ha3

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