Critical Malicious Code Vulnerability in integrator-filescrypt2025 Package

integrator-filescrypt2025 Updated 19 Nov 2025

Summary

17/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190508: Malicious code in integrator-filescrypt2025 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The integrator-filescrypt2025 package is an npm library designed for file encryption and decryption. It offers developers a straightforward way to secure sensitive data within their applications. However, this package has been found to contain malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the integrator-filescrypt2025 package. This code can compromise the entire system where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code has been confirmed by multiple sources, indicating that any machine running 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-filescrypt2025

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 effective workarounds for this vulnerability. The only recommended action is to remove the package entirely from your system.

Conclusion

The integrator-filescrypt2025 package has been identified as containing malicious code, posing severe risks to any system that utilizes it. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring for vulnerabilities, such as through Vulert, is recommended to maintain application security.

See every vulnerability recorded for integrator-filescrypt2025 →

Share this vulnerability

FAQ

You should remove the package immediately and rotate any secrets or keys stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and complete system compromise.

While removing the package is essential, there is no guarantee that all malicious software will be eliminated. It is crucial to rotate all secrets and keys.

Due to the confirmed presence of malicious code, it is advisable to avoid using this package in the future unless a trusted source provides a clean version.

How To Fix

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

npm uninstall integrator-filescrypt2025

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