Malicious Code Injection in official_perch_orange-47 Package

official_perch_orange-47 Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106558: Malicious code in official_perch_orange-47 (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 official_perch_orange-47 package is part of the npm ecosystem, typically used for various JavaScript applications. It is designed to facilitate the development process by providing reusable components. However, this package has been identified as part of a malicious campaign that exploits npm's publishing capabilities, leading to the proliferation of harmful scripts.

Vulnerability Detail

The vulnerability in the official_perch_orange-47 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 inflate developer reputation scores for token rewards, resulting in a polluted npm registry. The malicious payload can lead to the unintentional installation of compromised packages, potentially exposing applications to further security risks.

How To Fix

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

npm uninstall official_perch_orange-47

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

Conclusion

The official_perch_orange-47 package has been identified as containing malicious code that poses significant risks to applications using it. It is crucial to update or remove this package to safeguard your projects from potential vulnerabilities. Utilizing tools like Vulert can enhance your ability to monitor and manage open-source vulnerabilities effectively.

See every vulnerability recorded for official_perch_orange-47 →

Share this vulnerability

FAQ

The malicious code modifies package.json to remove private flags and generates random package names, which can lead to the installation of harmful variants.

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

Using this package can lead to the installation of compromised versions, exposing your application to security vulnerabilities and potential data breaches.

Regularly updating packages, using tools like Vulert for monitoring, and auditing dependencies can help prevent vulnerabilities from affecting your projects.

If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.

How To Fix

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

npm uninstall official_perch_orange-47

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