Critical Malicious Code Vulnerability in transform-spread Package

transform-spread Updated 18 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1574: Malicious code in transform-spread (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 transform-spread package is a utility in the npm ecosystem that is designed to facilitate the transformation of data structures. It is commonly used in JavaScript applications for spreading properties of objects. However, this package has been compromised, leading to significant security concerns for any application that relies on it.

Vulnerability Detail

The vulnerability originates from the presence of malicious code embedded within the transform-spread package. This code can fully compromise any computer that has the package installed, potentially allowing an attacker to gain access to sensitive information such as secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it contains code that appears to be malicious in nature. Users are advised to treat any system running this package as compromised.

How To Fix

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

npm uninstall transform-spread

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, if you need to maintain functionality while transitioning away from transform-spread, consider using alternative packages that provide similar functionality without the security risks. Always ensure to review the security status of any package before installation.

Conclusion

The transform-spread package has been identified as containing malicious code that poses a significant security risk. Users must take immediate action to remove the package and secure their systems. Regular monitoring for vulnerabilities, such as through Vulert, can help maintain the security of your applications.

See every vulnerability recorded for transform-spread →

Share this vulnerability

FAQ

Immediately remove the transform-spread package 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 affected by this vulnerability without requiring any signup.

Currently, there is no patched version available. The best course of action is to remove the package entirely.

Failing to address this vulnerability can lead to unauthorized access to sensitive data and complete compromise of the affected system.

No, it is highly recommended to stop using transform-spread due to the embedded malicious code.

How To Fix

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

npm uninstall transform-spread

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