Malicious Code Detected in grammarly-editor-sdk: A Critical Security Threat

grammarly-editor-sdk Updated 02 Oct 2025

Summary

22/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6092: Malicious code in grammarly-editor-sdk (npm). Affects grammarly-editor-sdk versions >= 4.5.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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The grammarly-editor-sdk is an npm package designed to integrate Grammarly's editing capabilities into applications. It allows developers to enhance user text input with advanced grammar and style suggestions. However, this package has been identified as containing malicious code that communicates with a domain associated with harmful activities, posing significant security risks to users and their systems.

Vulnerability Detail

The vulnerability in the grammarly-editor-sdk arises from embedded malicious code that can compromise the security of any system where the package is installed. This code may allow unauthorized access to sensitive information, including secrets and keys stored on the affected computer. The malicious nature of this code was confirmed through its association with a domain known for malicious activities, indicating a high level of risk for users who have this package installed. The vulnerability affects all versions starting from 0 up to 4.5.0 and beyond, making it critical for users to take immediate action.

How To Fix

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

npm uninstall grammarly-editor-sdk

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

Currently, there are no effective workarounds to mitigate the risks associated with the grammarly-editor-sdk. The only recommended action is to uninstall the package entirely.

Conclusion

The discovery of malicious code within the grammarly-editor-sdk poses a significant threat to users and their systems. Immediate action is required to uninstall the package and secure sensitive information. Continuous monitoring for vulnerabilities is essential to maintain software security.

See every vulnerability recorded for grammarly-editor-sdk →

Share this vulnerability

FAQ

The grammarly-editor-sdk is an npm package that integrates Grammarly's writing assistance features into applications, providing users with grammar and style suggestions.

The malicious code can compromise your system by allowing unauthorized access to sensitive information, potentially leading to data breaches and loss of control over your system.

If you have the grammarly-editor-sdk installed, you should uninstall it immediately and rotate any sensitive information stored on your system.

No, there is currently no patched version available for the grammarly-editor-sdk. The only solution is to remove the package completely.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall grammarly-editor-sdk

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