Malicious Code Vulnerability in baidu-src-test4 Package

baidu-src-test4 Updated 23 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192713: Malicious code in baidu-src-test4 (npm). Affects baidu-src-test4 versions 0.0.4. 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 baidu-src-test4 package is an npm library that is utilized for various functionalities in JavaScript applications. It is designed to facilitate certain features that enhance the development process. However, this package has been identified as containing malicious code, which poses significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the baidu-src-test4 package, specifically in version 0.0.4. This malicious code can lead to unauthorized access, data breaches, or other harmful actions within the application utilizing this package. The origin of this vulnerability is linked to the package's distribution through npm, where it was identified by security researchers from ReversingLabs.

How To Fix

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

npm uninstall baidu-src-test4

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

If immediate updating is not feasible, consider removing the baidu-src-test4 package from your project and replacing it with an alternative library that provides similar functionality without the associated risks.

Conclusion

The baidu-src-test4 package has been identified as containing malicious code, which poses serious security risks. It is crucial to update to a patched version or remove the package to safeguard your application. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for baidu-src-test4 →

Share this vulnerability

FAQ

The baidu-src-test4 package is an npm library used in JavaScript applications for various functionalities.

The malicious code can lead to unauthorized access and potential data breaches within applications that use this package.

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

It is advisable to check the package repository for any patched versions and update accordingly.

Consider removing the baidu-src-test4 package and replacing it with a safer alternative until you can update.

How To Fix

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

npm uninstall baidu-src-test4

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