Malicious Code Injection in technical-alonbio-tolamai: A Threat to npm Ecosystem

technical-alonbio-tolamai Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168904: Malicious code in technical-alonbio-tolamai (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 package 'technical-alonbio-tolamai' is part of a series of npm packages that have been associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious software.

Vulnerability Detail

This vulnerability originates from the package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially compromising other packages and applications that depend on them. The presence of such malicious scripts can lead to unauthorized access, data breaches, and a loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall technical-alonbio-tolamai

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 avoid using the 'technical-alonbio-tolamai' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like Vulert to monitor for vulnerabilities.

Conclusion

The 'technical-alonbio-tolamai' package poses a significant threat due to its malicious code designed to manipulate the npm registry. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities to maintain the security of your applications.

See every vulnerability recorded for technical-alonbio-tolamai →

Share this vulnerability

FAQ

The primary risk is the injection of malicious code that can compromise the integrity of your application and the npm registry.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Uninstall the package immediately using 'npm uninstall technical-alonbio-tolamai' and check your package-lock.json for any references.

Yes, consider looking for other npm packages that provide similar functionality but are verified to be safe.

Regularly audit your dependencies using tools like Vulert, and stay updated on security advisories related to npm packages.

How To Fix

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

npm uninstall technical-alonbio-tolamai

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