Malicious Code Detected in wei516-tpa: A Threat to LLM Safeguards

wei516-tpa Updated 03 Dec 2025

Summary

06/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191931: Malicious code in wei516-tpa (PyPI). Affects wei516-tpa versions 0.1.4 – 0.1.6. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'wei516-tpa' is designed to provide an MCP server functionality. However, it has been identified to contain malicious code that attempts to manipulate an LLM agent to bypass its safeguards. This raises concerns about the integrity and security of applications utilizing this package, as it may lead to unintended consequences in AI behavior.

Vulnerability Detail

The vulnerability originates from the package 'wei516-tpa', which masquerades as a legitimate MCP server but includes code aimed at compromising LLM safeguards. This malicious intent could allow attackers to exploit the package for unauthorized actions, potentially leading to data breaches or misuse of AI capabilities. The package was sourced from kam193 and has been flagged for its low-harm potential, categorized under pentesting and research.

How To Fix

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

pip uninstall wei516-tpa

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 measure, you can avoid using the 'wei516-tpa' package until a fix is confirmed. If you need to maintain functionality, consider using alternative packages that provide similar MCP server capabilities without the associated risks.

Conclusion

The 'wei516-tpa' package has been identified as containing malicious code that threatens LLM safeguards. Users are encouraged to update or remove the package to mitigate risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for wei516-tpa →

Share this vulnerability

FAQ

The vulnerability involves malicious code that attempts to manipulate LLM safeguards, posing a risk to applications using this package.

You can use the Vulert playground at Vulert Scanner to monitor and alert for open-source vulnerabilities in your software without needing to sign up.

It is advisable to update the package to the latest version or consider removing it until a fix is confirmed.

Detailed information can be found on the GitHub repository of the malicious packages or through the vulnerability report provided by OSSF.

Yes, the malicious code could potentially lead to unauthorized actions and data breaches if exploited.

How To Fix

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

pip uninstall wei516-tpa

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