Malicious Code Detected in cooni-expo Package - Security Alert

cooni-expo Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-17538: Malicious code in cooni-expo (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The cooni-expo package is a Node.js library designed for use in Expo applications, providing various functionalities to enhance development. However, it has been identified to contain malicious code, posing a significant risk to applications that utilize this package. Users of cooni-expo should be aware of its potential vulnerabilities and take necessary precautions.

Vulnerability Detail

The vulnerability in the cooni-expo package originates from the inclusion of malicious code that can compromise the security of applications using this package. This code may lead to unauthorized access, data breaches, or other malicious activities. The vulnerability is present in all versions starting from 0, making it critical for users to assess their dependency on this package and take immediate action.

How To Fix

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

npm uninstall cooni-expo

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 measure, you can avoid using the cooni-expo package until a secure version is released. Consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The cooni-expo package has been identified as containing malicious code, posing a significant risk to applications. Users are advised to remove the package and monitor for updates. Utilizing tools like Vulert can help in identifying vulnerabilities in your application effectively.

See every vulnerability recorded for cooni-expo →

Share this vulnerability

FAQ

cooni-expo is a Node.js library used in Expo applications to enhance development capabilities.

The malicious code can lead to unauthorized access and potential data breaches in applications using the package.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

Currently, there is no patched version available. It is advised to remove the package until a secure version is released.

Remove the cooni-expo package from your project immediately and consider using alternative packages until a secure version is available.

How To Fix

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

npm uninstall cooni-expo

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