Malicious Code Injection in mansila-tfla-magl Package - npm Vulnerability

mansila-tfla-magl Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159799: Malicious code in mansila-tfla-magl (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The 'mansila-tfla-magl' package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that alter package metadata and continuously republish variants, leading to pollution of the npm registry.

Vulnerability Detail

The vulnerability in the 'mansila-tfla-magl' package stems from its association with a malicious campaign that employs scripts to modify the package.json file. This includes removing private flags, changing version numbers, and generating random package names. The malicious payload can lead to a significant increase in the number of derivative packages in the npm registry, which can confuse developers and compromise the integrity of the ecosystem. The origin of this vulnerability is linked to the exploitation of npm's publishing mechanisms, which are manipulated to create a flood of low-quality packages.

How To Fix

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

npm uninstall mansila-tfla-magl

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 remove the 'mansila-tfla-magl' package from your project by executing the command: 'npm uninstall mansila-tfla-magl'. This will prevent any malicious code from executing while you seek a patched version or alternative solutions.

Conclusion

The 'mansila-tfla-magl' package has been identified as containing malicious code that can compromise the integrity of the npm ecosystem. It is crucial for developers to take immediate action by updating or removing the package to protect their projects from potential harm.

See every vulnerability recorded for mansila-tfla-magl →

Share this vulnerability

FAQ

It is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The vulnerability can lead to the pollution of the npm registry with low-quality packages, potentially confusing developers and compromising the integrity of your project.

You should update the package to the latest version or uninstall it to prevent any malicious activity.

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

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

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall mansila-tfla-magl

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