Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

data-version-servicenpm

data-version-service is a confirmed malicious npm package (MAL-2025-47057) that executes malicious code on install (malicious versions 1.7.3, 1.7.4, 1.7.5…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in data-version-service (npm)

MAL-2025-47057
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall data-version-service

What this malware does

The package communicates with a domain associated with malicious activity.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

7 flagged
1.7.31.7.41.7.51.7.61.7.71.7.81.7.9

Indicators of compromise (SHA-256)

67e15761c534191773c77884491eeda2d6062e9e52f77915cd7edbb117243bc0
bafc831846fa7c827604af1bec6e4d818c8fa1dba3042a93160a9f7892092596
c89747cc08cd3152da5f0b9335f37c48f083581727bb586327d1777f83dc1cae
a692c324b73743e41868fc3182c7cab0b43f13711ef9941989c29a0a8696ac08

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove data-version-service 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.

  3. Did it already run?

    If data-version-service 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.

  4. How O3 protects you

    O3 blocks data-version-service 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. data-version-service on npm has been identified as a malicious package (versions 1.7.3, 1.7.4, 1.7.5, 1.7.6, 1.7.7, 1.7.8, 1.7.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j4vf-pf88-gm2xRLMA-2025-04984RLUA-2026-01232

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks data-version-service-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.

Explore

data-version-service (npm) malicious package — MAL-2025-47057 | O3 Security