Malicious Code Vulnerability in spark-common Package

spark-common Updated 24 Sep 2026

Summary

22/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16537: Malicious code in spark-common (npm). Affects spark-common versions 1.0.0. 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 spark-common package is a widely used library in the npm ecosystem, designed to provide common functionalities for various applications. It is often utilized for its utility functions and shared components that enhance the development process. However, this package has been identified to contain malicious code, posing significant security risks to applications that depend on it.

Vulnerability Detail

The vulnerability in the spark-common package arises from the inclusion of malicious code that can compromise the integrity of applications utilizing this library. This malicious code can lead to unauthorized access, data breaches, or even complete system takeover. The issue was reported by ReversingLabs, indicating that the affected version is 1.0.0. The origin of this vulnerability is linked to the package's distribution through npm, where malicious actors can inject harmful code into widely used libraries.

How To Fix

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

npm uninstall spark-common

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, you can remove the spark-common package from your project if it is not critical to your application's functionality. Use the following command to uninstall it: npm uninstall spark-common. Alternatively, consider using a different package that offers similar functionalities without the associated risks.

Conclusion

The spark-common package has been identified to contain malicious code, posing serious security risks to applications that utilize it. It is crucial for developers to update to a patched version or consider alternative solutions to mitigate potential threats. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for spark-common →

Share this vulnerability

FAQ

The spark-common package is a library in the npm ecosystem that provides utility functions and shared components for application development.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By checking your package-lock.json file, Vulert can identify if your application is affected by this vulnerability.

If an immediate update is not possible, consider removing the package or using an alternative library until a secure version is available.

The vulnerability was reported by ReversingLabs, a cybersecurity firm specializing in threat intelligence and malware analysis.

Detailed information about this vulnerability can be found on the GitHub repository of malicious packages, specifically at the link provided in the vulnerability details.

How To Fix

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

npm uninstall spark-common

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