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

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

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

Remove @sas-dvr/ltjs-vav 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-vav — how do I know if it already compromised me?

If @sas-dvr/ltjs-vav 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-vav part of a known attack campaign?

Yes — @sas-dvr/ltjs-vav is associated with the RLMA-2025-02050 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-vav across my projects, lockfiles, and CI pipelines?

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

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

Malicious package

@sas-dvr/ltjs-vavnpm

Advisory published Mar 31, 2025Updated Apr 28, 2025

@sas-dvr/ltjs-vav is a confirmed malicious npm package (MAL-2025-2808) 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-vav (npm)

MAL-2025-2808

Immediate action

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

npm uninstall @sas-dvr/ltjs-vav

What this malware does

The OpenSSF Package Analysis project identified '@sas-dvr/ltjs-vav' @ 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)

f112f9f091de3ef1cc3a38c7a9cbb0bccc1949f7e38f8bb633cf9d5a06c646d7

a0d1c87d67170533ccb2e436be715d996375e773a154396d855b89d0d1cdc3bf

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @sas-dvr/ltjs-vav (2 malicious versions).
If you installed it — respond
Remove @sas-dvr/ltjs-vav 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-vav 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-vav 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-02050

Credits

OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks @sas-dvr/ltjs-vav-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