Malicious Code Injection in isolated_mastodon_requirement Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95121: Malicious code in isolated_mastodon_requirement (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 isolated_mastodon_requirement package is part of the npm ecosystem, primarily used for managing dependencies in JavaScript applications. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of this package is to facilitate interactions with the Mastodon social network, but it has been compromised to include harmful scripts that can manipulate project files.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the isolated_mastodon_requirement package. This code is designed to modify the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This can lead to significant security risks, including unauthorized access to sensitive information and the potential for further exploitation of affected systems.

How To Fix

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

npm uninstall isolated_mastodon_requirement

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 isolated_mastodon_requirement package from your project by executing the following command: npm uninstall isolated_mastodon_requirement. This will prevent the malicious code from executing until a secure version is available.

Conclusion

The isolated_mastodon_requirement package has been compromised with malicious code that poses significant risks to projects using it. It is crucial to update 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 isolated_mastodon_requirement →

Share this vulnerability

FAQ

It is an npm package used for managing dependencies related to the Mastodon social network, but it has been compromised with malicious code.

The malicious code modifies your package.json file, removes private flags, and can lead to unauthorized access and further exploitation.

Check the npm registry for the latest version of the isolated_mastodon_requirement package to see if a patched version is available.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall isolated_mastodon_requirement

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