Malicious Code Injection in masako-bender-lisa Package

masako-bender-lisa Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-160146: Malicious code in masako-bender-lisa (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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The masako-bender-lisa package is part of the npm ecosystem, typically used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially harming developers and users alike.

Vulnerability Detail

The vulnerability in the masako-bender-lisa package stems from its inclusion in a broader malicious campaign that modifies package.json files to remove private flags and change version numbers. It generates random package names and continuously republishes variants, leading to pollution of the npm registry. This can result in compromised developer reputations and the potential for malicious code execution in applications relying on this package.

How To Fix

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

npm uninstall masako-bender-lisa

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 avoid using the masako-bender-lisa package and replace it with a similar package that is verified and trusted. Always review the package's source and community feedback before integrating it into your project.

Conclusion

The masako-bender-lisa package poses a significant security risk due to its malicious code injection capabilities. It is crucial for developers to remove this package from their projects and monitor for any vulnerabilities using tools like Vulert. Staying informed and vigilant can help protect your applications from such threats.

See every vulnerability recorded for masako-bender-lisa →

Share this vulnerability

FAQ

The masako-bender-lisa package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.

This vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and functionality.

If you have installed the masako-bender-lisa package, you should uninstall it immediately and check for any other affected packages in your project.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Yes, you should look for well-reviewed and actively maintained packages that provide similar functionality without the associated risks.

How To Fix

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

npm uninstall masako-bender-lisa

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