Malicious Code Injection in adjacent_kiwi_replicate_automation Package

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99181: Malicious code in adjacent_kiwi_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 adjacent_kiwi_replicate_automation package is part of the npm ecosystem, designed to facilitate automation tasks. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package can inadvertently compromise the integrity of projects that depend on it, as it is associated with scripts that manipulate package metadata and publish unauthorized variants.

Vulnerability Detail

The vulnerability stems from the package's involvement in a token reward scheme that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. This malicious behavior modifies the package.json file by removing private flags, altering version numbers, and creating random package names, which can lead to reputation inflation and registry pollution. The origin of this issue is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall adjacent_kiwi_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 measure, you can avoid using the adjacent_kiwi_replicate_automation 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 adjacent_kiwi_replicate_automation package poses a significant risk due to its malicious code that alters package metadata and publishes unauthorized variants. It is essential to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the integrity of your applications.

See every vulnerability recorded for adjacent_kiwi_replicate_automation →

Share this vulnerability

FAQ

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

It can lead to unauthorized modifications of your package.json file and the proliferation of malicious packages in the npm registry.

Uninstall the package immediately using npm uninstall adjacent_kiwi_replicate_automation and consider using alternative packages.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.

How To Fix

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

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