Malicious Code Injection in murai-burt-sreat: A Threat to npm Ecosystem

murai-burt-sreat Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160989: Malicious code in murai-burt-sreat (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 package 'murai-burt-sreat' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior not only inflates developer reputation scores but also poses significant risks to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in 'murai-burt-sreat' stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This allows the package to continuously republish variants, polluting the npm registry and potentially leading to the distribution of compromised software. The origin of this vulnerability is linked to automated scripts that exploit the npm publishing process, making it a significant threat to developers and users alike.

How To Fix

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

npm uninstall murai-burt-sreat

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 avoid using the 'murai-burt-sreat' package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your npm packages using tools like 'npm audit' to identify and mitigate vulnerabilities.

Conclusion

The 'murai-burt-sreat' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for murai-burt-sreat →

Share this vulnerability

FAQ

'murai-burt-sreat' is a malicious npm package that is part of a campaign to inflate developer reputation scores through automated publishing of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially introducing compromised packages into your project, which can affect security and functionality.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without any signup.

If you have installed 'murai-burt-sreat', you should uninstall it immediately and audit your project for any other potentially malicious packages.

Yes, tools like 'npm audit' and Vulert can help you identify and manage vulnerabilities in your npm packages.

How To Fix

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

npm uninstall murai-burt-sreat

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