Malicious Code Injection in prior_sparrow-appteadev Package

prior_sparrow-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107293: Malicious code in prior_sparrow-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 prior_sparrow-appteadev package is part of the npm ecosystem, typically used for developing applications with JavaScript. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the prior_sparrow-appteadev package. This code is designed to automatically modify the package.json file by removing private flags, altering version numbers, and generating random package names. The scripts continuously republish these variants, leading to pollution of the npm registry and potential misuse of developer reputation scores. This can result in security risks for applications relying on this package, as it may introduce unverified and harmful code into their environments.

How To Fix

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

npm uninstall prior_sparrow-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 prior_sparrow-appteadev package from your project by executing: npm uninstall prior_sparrow-appteadev. This will prevent any malicious code from executing while you seek a secure alternative package.

Conclusion

The prior_sparrow-appteadev package has been identified as containing malicious code that can compromise application security. It is crucial to update or remove this package to protect your projects from potential threats. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for prior_sparrow-appteadev →

Share this vulnerability

FAQ

It is an npm package used in JavaScript applications, but it has been compromised with malicious code.

The malicious code can alter your package metadata and introduce unverified packages, leading to security vulnerabilities.

You should uninstall the package immediately and check for any updates or patches that may be available.

Yes, Vulert can monitor your package-lock.json file for vulnerabilities in real-time without requiring code access.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.

How To Fix

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

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