Malicious Code Injection in async-native-vortex-lynx: A Threat to npm Packages

async-native-vortex-lynx Updated 25 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-139629: Malicious code in async-native-vortex-lynx (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

async-native-vortex-lynx is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the distribution of token rewards through various npm packages. However, it has been compromised to include malicious scripts that manipulate package metadata and flood the npm registry with derivative packages, potentially harming developers' reputations and the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability stems from malicious code embedded in the async-native-vortex-lynx package. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The primary goal of this malicious activity is to inflate developer reputation scores for token rewards, leading to a polluted npm registry and potential security risks for users of these packages.

How To Fix

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

npm uninstall async-native-vortex-lynx

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 remove the async-native-vortex-lynx package from your project by executing: npm uninstall async-native-vortex-lynx. This will prevent any malicious scripts from executing while you assess the situation.

Conclusion

The async-native-vortex-lynx package has been identified as containing malicious code that poses a significant risk to npm users. It is crucial to take immediate action by updating or removing the package to protect your project from potential threats. Utilizing tools like Vulert can help you monitor for such vulnerabilities in the future.

See every vulnerability recorded for async-native-vortex-lynx →

Share this vulnerability

FAQ

async-native-vortex-lynx is an npm package involved in the tea.xyz token reward campaign, which has been compromised to include malicious code.

The malicious code modifies your package.json file, potentially leading to the publication of unauthorized packages and damaging your project's reputation.

You should immediately update or uninstall the async-native-vortex-lynx package to mitigate the risks associated with the vulnerability.

Yes, you can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall async-native-vortex-lynx

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.