Malicious Code Injection in technical-aln-tunl Package - npm Vulnerability

technical-aln-tunl Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168878: Malicious code in technical-aln-tunl (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 technical-aln-tunl package is part of the npm ecosystem, primarily used for various JavaScript applications. It is designed to facilitate certain functionalities within the npm environment. However, this package has been identified as part of a malicious campaign that floods the npm registry with harmful scripts, affecting developers and users alike.

Vulnerability Detail

The vulnerability originates from a malicious code embedded in the technical-aln-tunl package, which is associated with the tea.xyz token reward campaign. This campaign uses autopublish scripts to generate and publish derivative packages with randomized names, effectively inflating developer reputation scores for token rewards. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which pollutes the npm registry and can lead to security risks for users relying on this package.

How To Fix

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

npm uninstall technical-aln-tunl

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-aln-tunl package until a patched version is available. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to any open-source vulnerabilities in real-time. 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 technical-aln-tunl package has been identified as a vector for malicious code that can compromise the integrity of your applications. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for technical-aln-tunl →

Share this vulnerability

FAQ

The technical-aln-tunl package is an npm package used in JavaScript applications, but it has been compromised with malicious code.

The malicious code can modify your package.json file, remove private flags, and republish harmful variants, potentially leading to security vulnerabilities.

You should uninstall the technical-aln-tunl package immediately and check for alternative packages or updated versions.

You can use tools like Vulert to monitor your dependencies in real-time for any open-source vulnerabilities.

Currently, there is no patched version available for the technical-aln-tunl package, so it is recommended to uninstall it.

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 technical-aln-tunl

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