Critical Malicious Code Vulnerability in @suraj_h/medium-common Package

@suraj_h/medium-common Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191054: Malicious code in @suraj_h/medium-common (npm). Affects @suraj_h/medium-common versions 1.0.5. 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 @suraj_h/medium-common package is an npm library designed for common functionalities used in Medium-like applications. It provides various utilities that developers can leverage to enhance their applications. However, this package has been identified to contain malicious code, posing significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @suraj_h/medium-common package. This code can compromise the entire system where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that simply removing the package may not eliminate all traces of the compromise, as full control of the system may have been granted to an external entity.

How To Fix

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

npm uninstall @suraj_h/medium-common

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

Currently, there are no effective workarounds other than removing the package and securing the system. Ensure to monitor your system for any unusual activity following the removal.

Conclusion

The @suraj_h/medium-common package has been identified as containing malicious code that compromises the security of systems where it is installed. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for @suraj_h/medium-common →

Share this vulnerability

FAQ

You should immediately remove the package and rotate any secrets or keys stored on your system.

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

Keeping this package installed poses a significant risk as it may allow unauthorized access to your system and sensitive data.

While removing the package is essential, there is no guarantee that all malicious software will be removed. It is recommended to perform a thorough security audit of your system.

If a patched version is released, updating the package may resolve the vulnerability. However, it is crucial to remove the compromised version first.

How To Fix

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

npm uninstall @suraj_h/medium-common

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