Malicious Code Detected in angular-hw-cache Package

angular-hw-cache Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-14528: Malicious code in angular-hw-cache (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 angular-hw-cache package is a Node.js library designed to enhance caching mechanisms in Angular applications. It aims to improve performance by storing frequently accessed data in memory. However, this package has been identified to contain malicious code that could compromise the security of applications utilizing it.

Vulnerability Detail

The vulnerability in the angular-hw-cache package arises from the inclusion of malicious code that was intentionally introduced in version 0 and potentially affects all subsequent versions. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within applications that rely on this package. The origin of this vulnerability is linked to the package's maintainer, who has not addressed the issue, leaving users at risk.

How To Fix

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

npm uninstall angular-hw-cache

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 can replace the angular-hw-cache package with a different caching solution. For example, you can use the 'node-cache' package as follows:

  1. Install node-cache: npm install node-cache
  2. Replace the usage of angular-hw-cache in your code with node-cache functionality.

Conclusion

The angular-hw-cache package has been identified as containing malicious code that poses significant security risks to applications. Users are strongly advised to uninstall the package and consider alternative solutions to ensure the safety and integrity of their applications.

See every vulnerability recorded for angular-hw-cache →

Share this vulnerability

FAQ

angular-hw-cache is a Node.js library designed to enhance caching mechanisms in Angular applications.

The malicious code can lead to unauthorized access and potential data breaches within applications using the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

No, there is no patch available for the angular-hw-cache package. The best course of action is to uninstall it and use an alternative package.

Immediately uninstall the angular-hw-cache package and replace it with a secure alternative to mitigate any potential risks.

How To Fix

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

npm uninstall angular-hw-cache

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