Critical Malicious Code Vulnerability in hariprasath Package

hariprasath Updated 16 Mar 2026

Summary

16/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1465: Malicious code in hariprasath (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 hariprasath package is a Node.js library available through npm, designed for various utility functions. However, it has been identified to contain malicious code that compromises the security of any system where it is installed. This vulnerability poses a significant risk to users, as it can lead to unauthorized access and control over affected systems.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the hariprasath package. This code can fully compromise any computer that has the package installed, allowing an external entity to gain control over the system. Users are advised to treat any system with this package as compromised and to rotate all secrets and keys immediately. The malicious nature of this code falls under CWE-506, indicating that it contains embedded malicious code.

How To Fix

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

npm uninstall hariprasath

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

There are no effective workarounds for this vulnerability other than removing the package entirely. If you need similar functionality, consider looking for alternative packages that do not have known security issues.

Conclusion

The hariprasath package contains malicious code that poses a serious security risk. Users must uninstall the package immediately and rotate any sensitive information. Regular monitoring for vulnerabilities using tools like Vulert is recommended to maintain software security.

See every vulnerability recorded for hariprasath →

Share this vulnerability

FAQ

Immediately uninstall the hariprasath package using 'npm uninstall hariprasath' and rotate any sensitive credentials.

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

Keeping the hariprasath package installed can lead to unauthorized access to your system, data theft, and potential control by malicious actors.

No, there is currently no patched version available for the hariprasath package. The only solution is to uninstall it.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.

How To Fix

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

npm uninstall hariprasath

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