Malicious Code Vulnerability in pefsas-notthedevs Package

pefsas-notthedevs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107021: Malicious code in pefsas-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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The pefsas-notthedevs package is part of the npm ecosystem, often used for various JavaScript applications. It has been identified as part of a token reward campaign that exploits npm's publishing capabilities. This package, like others in the campaign, is designed to inflate developer reputation scores through the automatic generation and publishing of derivative packages.

Vulnerability Detail

The vulnerability originates from malicious code embedded in the pefsas-notthedevs package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The intent is to continuously republish these variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The ramifications include loss of trust in the npm registry, potential security risks for applications relying on these packages, and the proliferation of unwanted packages.

How To Fix

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

npm uninstall pefsas-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 remove the pefsas-notthedevs package from your project by executing: npm uninstall pefsas-notthedevs. This will prevent any malicious code from executing while you await a patched version.

Conclusion

The pefsas-notthedevs package contains malicious code that poses a significant risk to applications using it. It is crucial to take immediate action by updating or removing the package to safeguard your project from potential threats. Utilizing tools like Vulert can help maintain the security of your dependencies.

See every vulnerability recorded for pefsas-notthedevs →

Share this vulnerability

FAQ

pefsas-notthedevs is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores.

The malicious code modifies your package.json file and can lead to the automatic publication of unwanted packages, compromising your application's integrity.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground at Vulert Scanner.

If a patched version is not available, it is advisable to remove the package from your project until a secure version is released.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and keep your packages updated to the latest secure versions.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

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