Malicious Code Vulnerability in teeseest Package

teeseest Updated 24 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192878: Malicious code in teeseest (npm). Affects teeseest versions 1.6.2. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The teeseest package is a JavaScript library available through npm, primarily used for various utility functions in web development. It is designed to streamline tasks and enhance productivity for developers. However, this package has been identified as containing malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the teeseest package, specifically in version 1.6.2. This code can potentially compromise the security of applications by executing unauthorized actions, leading to data breaches or system exploitation. The malicious nature of this code makes it imperative for users to take immediate action to mitigate risks associated with its use.

How To Fix

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

npm uninstall teeseest

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 teeseest package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall teeseest'. This will prevent any potential exploitation from the malicious code.

Conclusion

The teeseest package has been identified as containing malicious code, which poses a significant threat to applications utilizing it. Users are urged to update or uninstall the package to safeguard their applications from potential exploitation. Regular monitoring of dependencies is essential to maintain security.

See every vulnerability recorded for teeseest →

Share this vulnerability

FAQ

Teeseest is a JavaScript library used for utility functions in web development, available through npm.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which monitors vulnerabilities in your package-lock.json.

If you are using teeseest, immediately update to the latest version or uninstall the package to avoid security risks.

Using a malicious package can lead to unauthorized access, data breaches, and exploitation of your application, compromising its integrity and security.

Regularly monitor your dependencies using tools like Vulert, and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall teeseest

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