Malicious Code Injection in secure_python-appteadev Package

secure_python-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-108496: Malicious code in secure_python-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 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 secure_python-appteadev package is part of the npm ecosystem, designed to facilitate Python application development. It is intended to provide developers with tools and libraries to streamline their workflow. However, this package has been compromised, making it susceptible to malicious activities that can affect the integrity of applications relying on it.

Vulnerability Detail

The vulnerability originates from a malicious payload embedded within the secure_python-appteadev package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It is part of a broader campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and pollution of the npm registry with malicious packages.

How To Fix

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

npm uninstall secure_python-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 secure_python-appteadev package from your project until a safe version is released. You can do this by executing: npm uninstall secure_python-appteadev. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The secure_python-appteadev package has been identified as containing malicious code that poses significant risks to developers and their applications. It is essential to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for secure_python-appteadev →

Share this vulnerability

FAQ

The malicious code modifies package.json, removes private flags, and generates random package names to inflate developer reputation scores.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.

Using the compromised package can lead to unauthorized access, exposure of sensitive data, and pollution of the npm registry.

Regularly update your packages, use tools like Vulert for monitoring, and review package dependencies for any known vulnerabilities.

If immediate updates are not possible, consider removing the package and using alternative solutions until a safe version is available.

How To Fix

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

npm uninstall secure_python-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