Malicious Code Vulnerability in astroarchitect Package

astroarchitect Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170926: Malicious code in astroarchitect (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The astroarchitect package is part of the npm ecosystem, primarily used for various development tasks. However, it has been identified as part of a malicious campaign that exploits npm's package publishing system. This package, like others in the campaign, is designed to inflate developer reputation scores through automated scripts that generate and publish numerous derivative packages.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the astroarchitect package, which is linked to the tea.xyz token reward campaign. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include pollution of the npm registry and potential security risks for developers who unknowingly use these compromised packages.

How To Fix

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

npm uninstall astroarchitect

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

Conclusion

The astroarchitect package has been identified as containing malicious code that poses a significant risk to developers. It is crucial to update or remove this package to safeguard your projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for astroarchitect →

Share this vulnerability

FAQ

Astroarchitect is an npm package used for various development tasks, but it has been compromised by malicious code.

The malicious code modifies your package.json, removes private flags, and generates random package names, which can lead to security vulnerabilities.

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

As a workaround, you can uninstall the astroarchitect package to prevent any malicious code from executing.

Detailed information can be found in the vulnerability report and on platforms like Vulert that track open-source vulnerabilities.

How To Fix

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

npm uninstall astroarchitect

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