Which versions of @sas-dvr/nova-graph are malicious?

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

How do I remediate @sas-dvr/nova-graph if I installed it?

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

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

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

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

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

Malicious package

@sas-dvr/nova-graphnpm

Advisory published Mar 31, 2025Updated Apr 28, 2025

@sas-dvr/nova-graph is a confirmed malicious npm package (MAL-2025-2807) 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/nova-graph (npm)

MAL-2025-2807

Immediate action

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

npm uninstall @sas-dvr/nova-graph

What this malware does

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

a004b8a712912389bc963af6af6b686564a92b57ef85becf55191418b57951c2

2ee49dd296a0db13b0118e5424d00aac99ea70cc3664bba504af096916e31998

424f7049bb090d3a1c8bc12675b3cfc9d22df66357c06925d297a303df6e16c8

Detection & response playbook

Malicious package

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

Credits

OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks @sas-dvr/nova-graph-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