Malicious Code Injection in papsdaya-notthedevs Package

papsdaya-notthedevs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106898: Malicious code in papsdaya-notthedevs (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 papsdaya-notthedevs package is part of the npm ecosystem, often utilized for various JavaScript projects. This package has been identified as part of a broader malicious campaign that exploits npm's package management system. Its primary function is to serve as a token reward mechanism, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the package being associated with a token reward campaign that floods the npm registry with malicious packages. These packages contain scripts designed to automatically generate and publish derivative packages with randomized names, effectively inflating 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 papsdaya-notthedevs

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 avoid using the papsdaya-notthedevs package altogether. If you must use it, consider isolating it in a separate environment to limit exposure to potential vulnerabilities.

Conclusion

The papsdaya-notthedevs package has been compromised, posing significant risks to projects that utilize it. Immediate action is required to remove the package and safeguard your application from potential threats. Utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.

See every vulnerability recorded for papsdaya-notthedevs →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

If you have this package installed, it can lead to the pollution of your npm registry and potentially expose your project to further security risks.

You should uninstall the package immediately and monitor your project for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json.

You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall papsdaya-notthedevs

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