Malicious Code Vulnerability in steady_squirrel-appteadev Package

steady_squirrel-appteadev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-109109: Malicious code in steady_squirrel-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 steady_squirrel-appteadev package is part of the npm ecosystem, typically used for various development purposes. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant pollution of the npm registry and potential security risks for developers using these packages.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the steady_squirrel-appteadev package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The malicious payload continuously republishes these variants, leading to a polluted npm registry. This can result in developers inadvertently using compromised packages, exposing their applications to security risks and undermining the integrity of the npm ecosystem.

How To Fix

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

npm uninstall steady_squirrel-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 avoid using the steady_squirrel-appteadev package and replace it with a trusted alternative. Additionally, you can use the following command to uninstall the package: npm uninstall steady_squirrel-appteadev.

Conclusion

The steady_squirrel-appteadev package contains malicious code that poses a significant risk to developers and their applications. It is crucial to remove this package and monitor for any potential vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software by providing real-time alerts for open-source vulnerabilities.

See every vulnerability recorded for steady_squirrel-appteadev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.

The malicious code can lead to the installation of compromised packages, which may introduce security vulnerabilities into your application.

You should uninstall the steady_squirrel-appteadev package immediately and monitor your application for any unusual behavior.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

How To Fix

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

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