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

service-config-endpoint-providernpm

service-config-endpoint-provider is a confirmed malicious npm package (MAL-2025-47086) that executes malicious code on install (malicious versions 1.17.9, 145.17.2, 145.17.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in service-config-endpoint-provider (npm)

MAL-2025-47086
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall service-config-endpoint-provider

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

8 flagged
1.17.9145.17.2145.17.3145.17.4145.17.5145.17.6145.17.7145.17.8

Indicators of compromise (SHA-256)

0879016c96750d8d2a0320e43955954e5f07cd7685cd65103101b1b9d3c3d7e5
7209cca3a2b1d6c171f024498db2a279ef389e93aa35feca779cbea0a59e982d
0dccfd3c0354729542c3d542f75156be637f139b5af89e5d8f5fda56ce4eae4f
b43367451e9ce58e9788678eda4c819773e69d78c4a98dc34a699fd5ce83b115

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 service-config-endpoint-provider (8 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging service-config-endpoint-provider across your stack and pipelines.

  2. If you installed it — respond

    Remove service-config-endpoint-provider 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 service-config-endpoint-provider 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 service-config-endpoint-provider 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. service-config-endpoint-provider on npm has been identified as a malicious package (versions 1.17.9, 145.17.2, 145.17.3, 145.17.4, 145.17.5, 145.17.6, 145.17.7, 145.17.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j958-xww7-x7vfRLMA-2025-05152RLUA-2026-01558

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks service-config-endpoint-provider-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

service-config-endpoint-provider (npm) malicious package — MAL-2025-47086 | O3 Security