Malicious Code Injection in curious_pinniped_dumbs Package

curious_pinniped_dumbs Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-101151: Malicious code in curious_pinniped_dumbs (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 curious_pinniped_dumbs package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development of applications 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 the creation of derivative packages.

Vulnerability Detail

The vulnerability in the curious_pinniped_dumbs package stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to automatically modify package.json files, removing private flags, changing version numbers, and generating random package names. This not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, leading to potential security breaches and loss of reputation.

How To Fix

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

npm uninstall curious_pinniped_dumbs

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 manually check your package-lock.json file for any instances of curious_pinniped_dumbs and remove it. Use the following command to uninstall the package: npm uninstall curious_pinniped_dumbs.

Conclusion

The curious_pinniped_dumbs package poses a significant risk due to its malicious nature, which can compromise the integrity of applications using it. It is essential to remove this package and monitor your project for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for curious_pinniped_dumbs →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to manipulate the npm registry.

Using this package can compromise your application's integrity and expose it to security risks, including unauthorized access and data manipulation.

You should immediately uninstall the curious_pinniped_dumbs package and check for any other compromised packages in your project.

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

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall curious_pinniped_dumbs

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