Malicious Code Injection in astronomad Package: npm Vulnerability Overview

astronomad Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170930: Malicious code in astronomad (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 astronomad package is part of the npm ecosystem, primarily used for various JavaScript applications. It is designed to facilitate certain functionalities within the npm environment. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages, impacting developers and users by inflating reputation scores through deceptive practices.

Vulnerability Detail

The vulnerability in the astronomad package stems from its association with a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to pollute the npm registry and can lead to significant security risks, including the potential for unauthorized access to sensitive data and the proliferation of malicious software.

How To Fix

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

npm uninstall astronomad

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 astronomad package from your project by executing 'npm uninstall astronomad'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The astronomad package poses a significant security risk due to its malicious code that alters package configurations and floods the npm registry. Users are advised to uninstall the package and monitor their applications for any vulnerabilities using tools like Vulert. Regular updates and audits of dependencies are essential for maintaining a secure development environment.

See every vulnerability recorded for astronomad →

Share this vulnerability

FAQ

The astronomad package contains malicious code that modifies package.json files and floods the npm registry with derivative packages.

You can use Vulert, which monitors vulnerabilities in real-time using your package-lock.json file. Visit Vulert Scanner to check your application without any signup.

Using the astronomad package can lead to unauthorized access to sensitive data, potential data corruption, and the introduction of other malicious software into your environment.

To prevent such vulnerabilities, regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid using unverified packages from the npm registry.

If you have used the astronomad package, it is crucial to uninstall it immediately and check your project for any unauthorized changes or vulnerabilities.

How To Fix

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

npm uninstall astronomad

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