Malicious Code Injection in 182-23run Package - HTML Redirection to Adult Sites

182-23run Updated 02 Oct 2025

Summary

03/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-5831: Malicious code in 182-23run (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The 182-23run package is an npm library designed for specific functionalities within JavaScript applications. However, it has been identified as malicious due to its capability to inject harmful HTML code. This vulnerability can redirect users to adult or malicious websites, posing significant security risks to applications that utilize this package.

Vulnerability Detail

The vulnerability arises from HTML injection present in the index.js file of the 182-23run package. This malicious code can redirect users to adult or potentially harmful sites, which can lead to data breaches, malware infections, or other security incidents. The issue is compounded by a YARA match on a suspicious URL, indicating the presence of known malicious patterns.

How To Fix

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

npm uninstall 182-23run

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, you can prevent the execution of the malicious code by removing the package from your project. Use the following command to uninstall it: npm uninstall 182-23run. This will mitigate the risk until a secure alternative is implemented.

Conclusion

The 182-23run package has been identified as malicious due to HTML injection vulnerabilities that redirect users to harmful sites. It is essential to remove this package from your projects and monitor for any secure alternatives or patches. Utilizing tools like Vulert can help in identifying such vulnerabilities in real-time.

See every vulnerability recorded for 182-23run →

Share this vulnerability

FAQ

182-23run is an npm package used in JavaScript applications, but it has been identified as malicious due to its HTML injection vulnerability.

The vulnerability involves HTML injection that redirects users to adult or malicious websites, posing security risks.

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.

If you are using the 182-23run package, it is recommended to uninstall it immediately and look for secure alternatives.

Currently, there is no patched version available. It is crucial to monitor the package repository for any updates.

How To Fix

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

npm uninstall 182-23run

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