Malicious Code Detected in astro-redis-telesto-test: A Threat to npm Users

astro-redis-telesto-test Updated 25 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-139616: Malicious code in astro-redis-telesto-test (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package astro-redis-telesto-test is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications by providing reusable code. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing system, leading to potential security risks for developers and their applications.

Vulnerability Detail

The vulnerability in astro-redis-telesto-test originates from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically modify package.json files, removing private flags, changing version numbers, and generating random package names. This behavior not only inflates developer reputation scores for token rewards but also pollutes the npm registry, making it difficult for developers to find legitimate packages. The malicious payload can lead to unauthorized access, data breaches, and a compromised development environment.

How To Fix

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

npm uninstall astro-redis-telesto-test

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 astro-redis-telesto-test package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The discovery of malicious code in the astro-redis-telesto-test package highlights the importance of vigilance when managing dependencies in software development. By understanding the nature of this vulnerability and taking proactive steps to mitigate risks, developers can protect their applications and maintain a secure development environment.

See every vulnerability recorded for astro-redis-telesto-test →

Share this vulnerability

FAQ

astro-redis-telesto-test is an npm package that has been identified as part of a malicious campaign targeting the npm registry.

The vulnerability can lead to unauthorized modifications of your package.json file, potentially compromising your application's security and integrity.

You should uninstall the astro-redis-telesto-test package immediately and review your project's dependencies for any other potentially malicious packages.

You can use Vulert, which monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities without any signup using the Vulert playground.

Yes, you should look for reputable packages that provide similar functionality but have a verified track record of security.

How To Fix

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

npm uninstall astro-redis-telesto-test

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.