Malicious Code Detected in examplereactnative76: npm Package Vulnerability

examplereactnative76 Updated 25 Feb 2026

Summary

24/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1028: Malicious code in examplereactnative76 (npm). Affects examplereactnative76 versions 0.0.8. 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

examplereactnative76 is an npm package designed for use in React Native applications. It provides various functionalities that developers can leverage to enhance their applications. However, version 0.0.8 of this package has been identified as malicious, posing significant security risks to users who integrate it into their projects.

Vulnerability Detail

The vulnerability in examplereactnative76 arises from its malicious nature, as identified by the OpenSSF Package Analysis project. The package communicates with a domain linked to malicious activities and executes commands that can lead to harmful consequences, such as data breaches or unauthorized access to systems. This vulnerability is particularly concerning for developers who may unknowingly incorporate this package into their applications, exposing them to potential exploitation.

How To Fix

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

npm uninstall examplereactnative76

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 examplereactnative76 package altogether until a secure version is released. Consider using alternative packages that offer similar functionalities without the associated risks.

Conclusion

The examplereactnative76 package has been flagged for malicious behavior, posing a serious risk to developers and their applications. It is crucial to take immediate action by removing the affected version and considering alternatives. Utilizing tools like Vulert can help in proactively monitoring for vulnerabilities in your projects.

See every vulnerability recorded for examplereactnative76 →

Share this vulnerability

FAQ

The vulnerability involves malicious code that communicates with harmful domains and executes potentially dangerous commands.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.

Remove the affected version of the package and consider updating to a patched version if available.

Yes, you can look for other npm packages that provide similar functionalities without the security risks associated with examplereactnative76.

Vulert uses the package-lock.json file to monitor and alert for vulnerabilities in open-source packages, ensuring your applications remain secure.

How To Fix

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

npm uninstall examplereactnative76

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