Malicious Code Vulnerability in tss12111 Package

tss12111 Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1869: Malicious code in tss12111 (npm). Affects tss12111 versions 1.0.0 – 1.0.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 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 tss12111 package is an npm module that is designed to provide specific functionalities for developers. However, it has been identified as containing malicious code that can compromise the security of applications utilizing this package. This vulnerability affects versions 1.0.0, 1.0.1, and 1.0.2, making it critical for users to be aware of its implications.

Vulnerability Detail

The vulnerability in the tss12111 package stems from the inclusion of malicious code that can execute unauthorized actions within the user's environment. This can lead to data breaches, unauthorized access to sensitive information, and potential system compromise. The malicious code was identified by ReversingLabs and is documented under the ID MAL-2026-1869. Users of this package are at risk if they do not take immediate action to mitigate the threat.

How To Fix

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

npm uninstall tss12111

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, users can remove the tss12111 package from their project until a secure version is confirmed. This can be done with the following command: npm uninstall tss12111. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The tss12111 package has been found to contain malicious code, posing significant risks to users. It is crucial to update or remove the package to protect your applications from potential threats. Regular monitoring and using tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for tss12111 →

Share this vulnerability

FAQ

The tss12111 package is an npm module used by developers for specific functionalities in their applications.

The vulnerability involves malicious code that can execute unauthorized actions, potentially compromising user data and system security.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

If immediate updates are not possible, consider uninstalling the package as a temporary measure and look for alternative packages.

The vulnerability was identified by ReversingLabs, a security research organization specializing in malware analysis.

How To Fix

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

npm uninstall tss12111

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