Malicious Code Exploit in precise_loon_dumbs Package

precise_loon_dumbs Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107191: Malicious code in precise_loon_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 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 precise_loon_dumbs package is part of the npm ecosystem, often used in JavaScript projects. It has been identified as part of a larger campaign that aims to exploit npm's publishing system. This package is designed to manipulate package metadata and inflate developer reputation scores through automated scripts.

Vulnerability Detail

The vulnerability stems from the package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a broader scheme to publish numerous derivative packages, thereby polluting the npm registry and potentially compromising the integrity of other projects that depend on it. The malicious payload can lead to unauthorized access and misuse of the npm ecosystem.

How To Fix

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

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

There are no direct workarounds for this vulnerability other than removing the affected package. Ensure that your project does not rely on precise_loon_dumbs or any of its derivatives.

Conclusion

The precise_loon_dumbs package poses a significant risk to projects using npm due to its malicious code that alters package metadata and publishes unauthorized derivatives. Immediate action is required to remove this package and safeguard your project from potential exploitation.

See every vulnerability recorded for precise_loon_dumbs →

Share this vulnerability

FAQ

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

The malicious code can modify your package.json file, potentially leading to unauthorized package publishing and reputation inflation.

You should uninstall the precise_loon_dumbs package immediately and check your project for any unauthorized changes.

Yes, you can use Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without needing to install any software.

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

How To Fix

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

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