Malicious Code Vulnerability in inter-site-components Package

inter-site-components Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1751: Malicious code in inter-site-components (npm). Affects inter-site-components versions 99.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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The inter-site-components package is a library used in npm ecosystems to facilitate inter-site communication and component sharing. It is designed to enhance modularity and reusability of web components across different sites. However, this package has been found to contain malicious code that poses significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability identified as MAL-2026-1751 stems from malicious code embedded within the inter-site-components package. This code can potentially lead to unauthorized access, data breaches, or exploitation of the affected systems. The malicious nature of this vulnerability was reported by ReversingLabs, which discovered that version 99.0.0 of the package contains harmful elements that can compromise the integrity of applications relying on it.

How To Fix

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

npm uninstall inter-site-components

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 measure, you can remove the inter-site-components package from your project until a secure version is released. You can do this by running the following command: npm uninstall inter-site-components. This will prevent any potential exploitation while you await a fix.

Conclusion

The inter-site-components package has been identified as containing malicious code, posing a significant risk to applications that utilize it. It is essential to update or remove the package to safeguard your application from potential threats. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for inter-site-components →

Share this vulnerability

FAQ

The inter-site-components package is a library used in npm for facilitating communication and sharing components between different web applications.

The MAL-2026-1751 vulnerability involves malicious code within the inter-site-components package that can lead to security breaches.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If you are using version 99.0.0 of the inter-site-components package, you should update it to a secure version as soon as possible.

The vulnerability was reported by ReversingLabs, a security research firm specializing in identifying malicious packages.

How To Fix

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

npm uninstall inter-site-components

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