Critical Malicious Code Vulnerability in ts-relay-cursor-paging Package

ts-relay-cursor-paging Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191437: Malicious code in ts-relay-cursor-paging (npm). Affects ts-relay-cursor-paging versions 2.1.1. 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 ts-relay-cursor-paging package is an npm library designed for cursor-based pagination in GraphQL APIs. It provides developers with a streamlined way to implement pagination, enhancing the performance and usability of their applications. However, this package has been compromised, making it a significant security risk for any project that relies on it.

Vulnerability Detail

The vulnerability stems from the package being infected by the Sha1-Hulud: The Second Coming NPM worm. This malicious code can steal sensitive tokens and credentials, publishing them to GitHub. It can also propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. Furthermore, there is a risk of the worm destroying the user's home directory, leading to severe data loss.

How To Fix

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

npm uninstall ts-relay-cursor-paging

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, avoid using the ts-relay-cursor-paging package until it has been confirmed safe. Consider using alternative libraries for cursor-based pagination in your GraphQL APIs.

Conclusion

The ts-relay-cursor-paging package has been compromised by a malicious worm, posing serious security risks to any application using it. Immediate action is required to remove the package and secure any affected systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for ts-relay-cursor-paging →

Share this vulnerability

FAQ

Immediately remove the package and rotate any secrets or keys stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Failure to address this vulnerability could lead to unauthorized access to sensitive data, potential data loss, and compromise of your development environment.

Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with security advisories related to the packages you use.

The malicious code originated from the Sha1-Hulud: The Second Coming NPM worm, which has been known to compromise npm packages.

How To Fix

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

npm uninstall ts-relay-cursor-paging

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