Malicious Code Injection in only_prawn-silentdev Package

only_prawn-silentdev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106735: Malicious code in only_prawn-silentdev (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 only_prawn-silentdev 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 components. However, it has been identified as part of a malicious campaign that aims to manipulate the npm registry and inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability in the only_prawn-silentdev package arises from its association with a malicious campaign that modifies package.json files to remove private flags and change version numbers. This allows the package to continuously republish variants with randomized names, polluting the npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to generate and publish derivative packages. The ramifications include potential security risks for developers using this package, as it can lead to the installation of compromised software and affect the integrity of the npm ecosystem.

How To Fix

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

npm uninstall only_prawn-silentdev

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, avoid using the only_prawn-silentdev package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert, which can alert you to vulnerabilities in real-time without requiring code access or installation.

Conclusion

The only_prawn-silentdev package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers and their projects. It is crucial to remove this package and monitor your dependencies to maintain the security of your applications. Utilizing tools like Vulert can help you stay informed about potential vulnerabilities in real-time.

See every vulnerability recorded for only_prawn-silentdev →

Share this vulnerability

FAQ

The only_prawn-silentdev package is an npm package used in JavaScript development, but it has been identified as malicious due to its involvement in a campaign that manipulates the npm registry.

This vulnerability can lead to the installation of compromised software, affecting the security and integrity of your project and potentially exposing it to further risks.

You should uninstall the only_prawn-silentdev package immediately and check for any dependencies that may rely on it. Update your project to remove any potential risks.

Yes, you can use tools like Vulert to monitor your project's dependencies in real-time for open-source vulnerabilities without requiring code access or installation.

You can find detailed information about this vulnerability on the Vulert website or by checking the npm registry for updates regarding the only_prawn-silentdev package.

How To Fix

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

npm uninstall only_prawn-silentdev

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