Critical Malicious Code Vulnerability in android_teminator_x Package

android_teminator_x Updated 19 Dec 2025

Summary

19/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192620: Malicious code in android_teminator_x (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The android_teminator_x package is a Node.js library designed for Android development tasks. It provides various utilities to streamline the development process. However, this package has been identified as containing malicious code that compromises the security of systems where it is installed, making it a significant risk for developers and organizations using it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the android_teminator_x package. This code can lead to full system compromise, allowing unauthorized access to sensitive information such as secrets and keys stored on the affected machine. The origin of this vulnerability is linked to the package's distribution through npm, where it was flagged by security researchers. Users should be aware that simply removing the package may not eliminate all traces of the malicious software, as it may have already granted control to an external entity.

How To Fix

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

npm uninstall android_teminator_x

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

There are no effective workarounds for this vulnerability other than removing the package entirely. Users should ensure that their systems are secure and monitor for any signs of compromise.

Conclusion

The android_teminator_x package has been identified as containing malicious code, posing a serious risk to users. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring of dependencies and using tools like Vulert can help prevent future vulnerabilities.

See every vulnerability recorded for android_teminator_x →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

No, there is currently no patched version available for this package. The only course of action is to uninstall it.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

While many packages on npm are safe, it is essential to conduct thorough security checks and monitor for vulnerabilities regularly.

How To Fix

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

npm uninstall android_teminator_x

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