Malicious Code Injection in mansila-tila-mala Package

mansila-tila-mala Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-159845: Malicious code in mansila-tila-mala (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The mansila-tila-mala package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others, is intended to facilitate certain functionalities within applications. However, it has been identified as part of a malicious campaign that exploits npm's package management system, leading to severe security risks for developers and users alike.

Vulnerability Detail

The vulnerability in the mansila-tila-mala package originates from its association with the tea.xyz token reward campaign. This campaign has led to the proliferation of packages that contain malicious scripts designed to manipulate package metadata. Specifically, the malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, which can lead to the pollution of the npm registry. The ramifications include potential security breaches, unauthorized access to sensitive data, and a compromised development environment.

How To Fix

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

npm uninstall mansila-tila-mala

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 mansila-tila-mala package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The mansila-tila-mala package poses significant security risks due to its malicious code. It is essential for developers to remove this package from their projects and utilize monitoring tools like Vulert to ensure their applications remain secure. Regular updates and vigilance are key to maintaining a safe development environment.

See every vulnerability recorded for mansila-tila-mala →

Share this vulnerability

FAQ

The mansila-tila-mala package is an npm package used in JavaScript development, but it has been identified as malicious.

The vulnerability can lead to unauthorized changes in your package metadata, potentially compromising your application's security.

You should uninstall the mansila-tila-mala package immediately and check for any other affected packages in your project.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.

How To Fix

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

npm uninstall mansila-tila-mala

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