NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

ts-relay-cursor-pagingnpm

Advisory published Updated

ts-relay-cursor-paging is a confirmed malicious npm package (MAL-2025-191437) that steals credentials and exfiltrates sensitive data (malicious version 2.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ts-relay-cursor-paging (npm)

MAL-2025-191437
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall ts-relay-cursor-paging

What this malware does

The package ts-relay-cursor-paging was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged
2.1.1

Indicators of compromise (SHA-256)

ad95e08dbb91eef4e332f1b3b240bc5c98e01d96f215a23c6dcec9c8175590f7
0e87be322f5f45a7ca5517fbf03b5b86229a93ba0a49cd010550d6fb31437405
b8294a2a4839120e6ebab7dabdd05718b4208ab8fcf4be3cb922929a79e25764

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for ts-relay-cursor-paging (version 2.1.1).

  2. If you installed it — respond

    ts-relay-cursor-paging is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If ts-relay-cursor-paging was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. ts-relay-cursor-paging on npm has been identified as a malicious package (version 2.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r9rr-c7vq-r642

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks ts-relay-cursor-paging-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
ts-relay-cursor-paging (npm) malicious package — MAL-2025-191437 | O3 Security