Critical Malicious Code Vulnerability in doggus Package

doggus Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-18591: Malicious code in doggus (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The doggus package is an npm library designed for specific functionalities within JavaScript applications. It is used by developers for its ease of integration and utility features. However, it has been identified to contain malicious code that poses a significant risk to applications utilizing this package.

Vulnerability Detail

The vulnerability in the doggus package stems from the inclusion of malicious code that can compromise the security of applications. This code was introduced in version 0 and can lead to unauthorized access, data breaches, or other harmful actions within the software environment. The presence of such code can severely affect the integrity and confidentiality of user data.

How To Fix

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

npm uninstall doggus

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 doggus package in your project until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The doggus package has been identified as containing malicious code, posing significant risks to applications that utilize it. It is essential to remove this package and monitor for updates or alternatives to ensure the security of your software.

See every vulnerability recorded for doggus →

Share this vulnerability

FAQ

The doggus package is an npm library used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By checking your package-lock.json file, you can determine if your application is affected by this vulnerability.

If you are using the doggus package, it is crucial to remove it from your project and look for secure alternatives until a patched version is available.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Using the doggus package can lead to unauthorized access, data breaches, and other harmful actions that compromise the security of your application.

How To Fix

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

npm uninstall doggus

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