Malicious Code Detected in npm Package 'cogler'

cogler Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17267: Malicious code in cogler (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 'cogler' package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers for various tasks, but its recent discovery of malicious code poses a significant threat. The package's attributes include ease of integration and a range of features that make it appealing to developers. However, the presence of malicious code undermines its reliability and security.

Vulnerability Detail

The vulnerability in the 'cogler' package arises from the inclusion of malicious code that can compromise the security of applications using this package. This code can lead to unauthorized access, data breaches, or other harmful actions within the application environment. The vulnerability was introduced in version 0 and affects all subsequent versions, making it critical for users to address this issue promptly.

How To Fix

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

npm uninstall cogler

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, users can remove the 'cogler' package from their project until a secure version is released. This can be done using the command: 'npm uninstall cogler'. Alternatively, consider using a different package that provides similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the 'cogler' npm package presents a serious security risk for developers. Immediate action is required to mitigate this vulnerability by uninstalling the package and monitoring for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications.

See every vulnerability recorded for cogler →

Share this vulnerability

FAQ

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

If you are using 'cogler', you should uninstall the package immediately and monitor for updates or patches that address the vulnerability.

As of now, a patched version has not been released. Users should keep an eye on the package repository for updates.

Using a package with malicious code can lead to unauthorized access, data breaches, and potential harm to your application and its users.

How To Fix

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

npm uninstall cogler

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