Malicious Code Injection in ordinary_lemming-appteadev Package

ordinary_lemming-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106774: Malicious code in ordinary_lemming-appteadev (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 ordinary_lemming-appteadev package is part of the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry by generating and publishing derivative packages with randomized names. This behavior is linked to the tea.xyz token reward initiative, which incentivizes developers to inflate their reputation scores through deceptive practices.

Vulnerability Detail

The vulnerability stems from malicious code embedded within the ordinary_lemming-appteadev package. This code modifies the package.json file to remove private flags, alters version numbers, and creates random package names, leading to the continuous republishing of these variants. This not only pollutes the npm registry but also poses risks to developers who may unknowingly use these compromised packages, potentially leading to security breaches and 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 ordinary_lemming-appteadev

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 ordinary_lemming-appteadev package from your project until a secure version is released. Use the following command to uninstall it: 'npm uninstall ordinary_lemming-appteadev'. Additionally, consider using Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The ordinary_lemming-appteadev package has been compromised with malicious code that poses significant risks to developers and their projects. It is crucial to take immediate action by updating or removing the package and utilizing tools like Vulert for ongoing vulnerability monitoring.

See every vulnerability recorded for ordinary_lemming-appteadev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

This vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.

You should uninstall the package immediately and monitor your project for any signs of compromise.

Yes, you can use Vulert, which allows you to monitor and alert for open-source vulnerabilities in real-time using just your package-lock.json.

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

How To Fix

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

npm uninstall ordinary_lemming-appteadev

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