Critical Malicious Code Vulnerability in spark-ar-core-libs Package

spark-ar-core-libs Updated 08 Jan 2026

Summary

07/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-145: Malicious code in spark-ar-core-libs (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 spark-ar-core-libs package is a library used in the development of augmented reality applications, primarily for the Spark AR platform. It provides essential functionalities for creating AR effects and experiences. However, this package has been identified as containing malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the spark-ar-core-libs package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that even after removal of the package, there may be residual effects, as full control of the computer may have been handed over to an external entity. Users are advised to treat any system with this package as fully compromised.

How To Fix

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

npm uninstall spark-ar-core-libs

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 and secure the system.

Conclusion

The discovery of malicious code in the spark-ar-core-libs package poses a serious threat to users and developers. Immediate action is required to remove the package and secure any compromised systems. Regular monitoring and vulnerability checks, such as those provided by Vulert, can help maintain the security of your applications.

See every vulnerability recorded for spark-ar-core-libs →

Share this vulnerability

FAQ

You should remove the spark-ar-core-libs package immediately and rotate any sensitive information stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is impacted by this vulnerability without needing to sign up.

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, you should also rotate all secrets and keys from a secure device, as the malicious code may have already compromised your system.

Yes, you can continue using other packages, but ensure that they are not dependent on spark-ar-core-libs. Monitor your application for any further vulnerabilities.

How To Fix

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

npm uninstall spark-ar-core-libs

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