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

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

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

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

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

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

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

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

Malicious package

@sas-dvr/ltjs-sasicunpm

Advisory published Apr 23, 2025Updated Apr 23, 2025

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

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

MAL-2025-3305

Immediate action

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

npm uninstall @sas-dvr/ltjs-sasicu

Malicious versions

2 flagged

1.0.0118.3.0

Indicators of compromise (SHA-256)

ff545d93d915ff52b964b166cbf0b83629e4234e87f4c0c9873141ca832a5b0c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @sas-dvr/ltjs-sasicu (2 malicious versions).
If you installed it — respond
Remove @sas-dvr/ltjs-sasicu 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-sasicu 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-sasicu on npm has been identified as a malicious package (versions 1.0.0, 118.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-02049

Credits

ReversingLabs · finder

Detect & block this

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