Critical Malicious Code Vulnerability in integrator-2830 Package

integrator-2830 Updated 19 Nov 2025

Summary

17/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190507: Malicious code in integrator-2830 (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 integrator-2830 package is an npm library designed for integration tasks within JavaScript applications. It provides various functionalities that facilitate the seamless integration of different services and APIs. However, this package has been compromised, leading to the introduction of malicious code that poses significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the integrator-2830 package. This code can compromise any computer that has the package installed or running, potentially allowing unauthorized access to sensitive information, including secrets and keys. The malicious nature of the code has been confirmed by security sources, indicating that systems using this package should be considered fully compromised.

How To Fix

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

npm uninstall integrator-2830

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 workaround, it is recommended to uninstall the integrator-2830 package using the command: npm uninstall integrator-2830. However, be aware that simply removing the package may not eliminate all malicious software that may have been installed as a result.

Conclusion

The integrator-2830 package has been identified as containing malicious code, posing significant risks to any systems using it. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for integrator-2830 →

Share this vulnerability

FAQ

The integrator-2830 package is an npm library used for integration tasks in JavaScript applications, facilitating the connection between various services and APIs.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially leading to further security breaches.

You should immediately uninstall the integrator-2830 package and rotate any secrets or keys stored on the affected system.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and ensure to keep your packages updated to their latest versions.

How To Fix

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

npm uninstall integrator-2830

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