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

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

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

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

If @sas-dvr/ltjs-bird was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

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

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

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @sas-dvr/ltjs-bird (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sas-dvr/ltjs-bird across your stack and pipelines.

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

Malicious package

@sas-dvr/ltjs-birdnpm

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

MAL-2025-2804

Immediate action

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

npm uninstall @sas-dvr/ltjs-bird

What this malware does

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

bed916c128062e6e46a4741aecf296a1d3898ba06f3f0a818b19c8e90cd69f5b

1dc0ef62280a12d320de55c633b7d88cfe5ec62ed1ebbc656e04f29aa823dd43

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @sas-dvr/ltjs-bird (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sas-dvr/ltjs-bird across your stack and pipelines.
If you installed it — respond
Remove @sas-dvr/ltjs-bird 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-bird was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @sas-dvr/ltjs-bird before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @sas-dvr/ltjs-bird 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-02046

Credits

OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

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