Malicious Code Injection in interior_peafowl-strongdev Package

interior_peafowl-strongdev Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104341: Malicious code in interior_peafowl-strongdev (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The interior_peafowl-strongdev package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate development by providing reusable code modules. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing mechanisms, thereby compromising the integrity of the package registry.

Vulnerability Detail

The vulnerability stems from the package being involved in a token reward campaign that floods npm with malicious packages. It contains scripts designed to automatically generate and publish derivative packages with randomized names, which can inflate developer reputation scores. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, leading to pollution of the npm registry and potential security risks for users who inadvertently install these packages.

How To Fix

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

npm uninstall interior_peafowl-strongdev

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 workaround, you can avoid using the interior_peafowl-strongdev package altogether. If it is a dependency of another package, consider removing that package or replacing it with a more reputable alternative.

Conclusion

The interior_peafowl-strongdev package poses a significant security risk due to its involvement in a malicious npm campaign. Users are advised to remove this package and monitor their dependencies for any signs of compromise. Utilizing tools like Vulert can help in identifying vulnerabilities in real-time.

See every vulnerability recorded for interior_peafowl-strongdev →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to exploit npm's publishing mechanisms.

If you have this package installed, your application may be at risk of using malicious code that could compromise its security and integrity.

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

Remove the package immediately and consider replacing it with a more secure alternative. Additionally, keep your dependencies updated.

Currently, there is no specific patched version available for the interior_peafowl-strongdev package. It is best to remove it from your project.

How To Fix

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

npm uninstall interior_peafowl-strongdev

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