Malicious Code Injection in masan-ofali-baivula Package - npm Vulnerability

masan-ofali-baivula Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160171: Malicious code in masan-ofali-baivula (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 masan-ofali-baivula package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and potential security risks for users relying on these packages.

Vulnerability Detail

The vulnerability in the masan-ofali-baivula package originates from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants, thereby polluting the npm registry. This behavior can lead to the installation of compromised packages, exposing users to potential security threats and undermining the integrity of the npm ecosystem.

How To Fix

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

npm uninstall masan-ofali-baivula

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 workaround, you can remove the masan-ofali-baivula package from your project by executing the command: npm uninstall masan-ofali-baivula. This will prevent any potential malicious code from executing until a secure version is available.

Conclusion

The masan-ofali-baivula package poses a significant security risk due to its malicious code injection. Users are advised to take immediate action by uninstalling the package and monitoring their applications for vulnerabilities. Utilizing tools like Vulert can enhance security by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for masan-ofali-baivula →

Share this vulnerability

FAQ

The masan-ofali-baivula package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

This vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your application.

If you have installed the masan-ofali-baivula package, it is recommended to uninstall it immediately and check for any updates or patches.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground.

To prevent future vulnerabilities, regularly update your packages, monitor your dependencies, and utilize tools like Vulert for real-time vulnerability alerts.

How To Fix

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

npm uninstall masan-ofali-baivula

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