Malicious Code Injection in advisory_asp_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99216: Malicious code in advisory_asp_replicate_automation (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 advisory_asp_replicate_automation package is part of the npm ecosystem, typically used for automation tasks in JavaScript applications. It is designed to facilitate various automation processes, but it has been compromised by malicious actors. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with harmful packages aimed at inflating developer reputation scores.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the advisory_asp_replicate_automation 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, polluting the npm registry and potentially leading to reputational damage for developers and security risks for applications using these packages.

How To Fix

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

npm uninstall advisory_asp_replicate_automation

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

Conclusion

The advisory_asp_replicate_automation package has been compromised with malicious code that poses significant risks to applications using it. It is crucial to update or remove the package to mitigate these risks. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for advisory_asp_replicate_automation →

Share this vulnerability

FAQ

It is an npm package used for automation tasks, but it has been compromised with malicious code.

The malicious code modifies your package.json file and can lead to the publication of harmful packages, affecting your application's integrity.

You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

As a temporary measure, you can uninstall the package to prevent any malicious activity until a secure version is released.

Detailed information can be found in the vulnerability report on the GitHub repository for malicious packages.

How To Fix

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

npm uninstall advisory_asp_replicate_automation

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