Malicious Code Vulnerability in hushlockler: A Critical Security Threat

hushlockler Updated 02 Oct 2025

Summary

31/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6423: Malicious code in hushlockler (npm). Affects hushlockler versions 13.39.2. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

hushlockler is an npm package designed for managing and locking dependencies in JavaScript applications. It is widely used due to its ability to streamline the development process by ensuring consistent environments across different setups. However, this package has been identified to contain malicious code, posing significant security risks to users who rely on it.

Vulnerability Detail

The vulnerability identified as MAL-2025-6423 originates from a malicious code injection in version 13.39.2 of the hushlockler package. This code can lead to unauthorized access to sensitive data, potential data breaches, and exploitation of the affected systems. The malicious behavior can compromise the integrity of applications that utilize this package, 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 hushlockler

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 measure, users can avoid using the affected version of hushlockler (13.39.2) by uninstalling it and replacing it with an alternative package or an earlier, unaffected version. Use the following command to uninstall: npm uninstall hushlockler.

Conclusion

The discovery of malicious code in the hushlockler package highlights the importance of maintaining vigilance in software dependencies. Users are urged to update their packages promptly and utilize tools like Vulert for ongoing monitoring to safeguard their applications against potential threats.

See every vulnerability recorded for hushlockler →

Share this vulnerability

FAQ

hushlockler is an npm package used for managing and locking dependencies in JavaScript applications.

This vulnerability involves malicious code that can lead to unauthorized access and data breaches.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

You should immediately update the hushlockler package to the latest version using the command: npm install hushlockler@latest.

Yes, Vulert provides real-time monitoring and alerts for open-source vulnerabilities using just your package-lock.json file.

How To Fix

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

npm uninstall hushlockler

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