Malicious Code Vulnerability in technical-alonbio-tolamaiui Package

technical-alonbio-tolamaiui Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168905: Malicious code in technical-alonbio-tolamaiui (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 technical-alonbio-tolamaiui package is part of the npm ecosystem, primarily used for developing user interfaces. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system. This package is associated with the tea.xyz token reward scheme, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

This vulnerability arises from malicious code embedded within the technical-alonbio-tolamaiui package. The code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of projects relying on this package. The origin of this issue is linked to a broader campaign that floods npm with malicious packages, undermining trust in the ecosystem.

How To Fix

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

npm uninstall technical-alonbio-tolamaiui

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, consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package dependencies using tools like Vulert, which analyzes your package-lock.json file for vulnerabilities in real-time.

Conclusion

The technical-alonbio-tolamaiui package has been identified as containing malicious code that can compromise npm projects. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for technical-alonbio-tolamaiui →

Share this vulnerability

FAQ

It is an npm package used for building user interfaces, but it has been compromised with malicious code.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing unwanted changes.

You should uninstall the package immediately and check for any updates or alternatives that are secure.

Yes, regularly monitor your dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time.

You can use the Vulert playground at Vulert Scanner to analyze your application for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall technical-alonbio-tolamaiui

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