Which versions of @sas-dvr/ltjs-gtl are malicious?

The following npm versions of @sas-dvr/ltjs-gtl are flagged malicious: 1.0.0, 132.0.0. Treat any of these as compromised.

How do I remediate @sas-dvr/ltjs-gtl if I installed it?

Remove @sas-dvr/ltjs-gtl from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @sas-dvr/ltjs-gtl — how do I know if it already compromised me?

If @sas-dvr/ltjs-gtl 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.

Is @sas-dvr/ltjs-gtl part of a known attack campaign?

Yes — @sas-dvr/ltjs-gtl is associated with the RLMA-2025-02048 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @sas-dvr/ltjs-gtl across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @sas-dvr/ltjs-gtl (2 malicious versions).

Part of a larger attack: @sas-dvr published 8 malicious packages. See the full campaign →

Malicious package

@sas-dvr/ltjs-gtlnpm

Advisory published Mar 31, 2025Updated Apr 28, 2025

@sas-dvr/ltjs-gtl is a confirmed malicious npm package (MAL-2025-2805) that executes malicious code on install (malicious versions 1.0.0, 132.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sas-dvr/ltjs-gtl (npm)

MAL-2025-2805

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @sas-dvr/ltjs-gtl

What this malware does

The OpenSSF Package Analysis project identified '@sas-dvr/ltjs-gtl' @ 132.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

1.0.0132.0.0

Indicators of compromise (SHA-256)

d9918a0240fbc144d32b7ca3a4fc2ba3da6b8483a21dc82007c079d5d1a8f394

590d9654b9fef2a4c23a65543bd772d8aa4c0b3262912a102d66720d6cd50b78

a718d569bcabd95421ae3f84b4048148dc1edd2c4892b9f029b013f0b6504714

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @sas-dvr/ltjs-gtl (2 malicious versions).
If you installed it — respond
Remove @sas-dvr/ltjs-gtl from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @sas-dvr/ltjs-gtl 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. @sas-dvr/ltjs-gtl on npm has been identified as a malicious package (versions 1.0.0, 132.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-02048

Credits

OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks @sas-dvr/ltjs-gtl-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database