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

basic-validator-pronpm

basic-validator-pro is a confirmed malicious npm package (MAL-2025-47175) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in basic-validator-pro (npm)

MAL-2025-47175
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall basic-validator-pro

What this malware does

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.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.7

Indicators of compromise (SHA-256)

a065e2ce3dcaa4245e9bd8873e7878385dbe7a3fe9aa7276ae5ac89686209889
abc6eea27c6078683a4330d244692ca691e2d18892b0fc021fe2f2400c6acfc9
dbd4c75b355a9c61e940c55818fec833ebe9eb398b4468b980526339dd3a0946
ac56c9ec44dbff4a72e7173d67cea750f08e9cf85828c4e0e9aac870fe93bf64
efbbee956edb528aa5485810dd5cf54dd807df90c2b664bec952358e89c052b0

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

  2. If you installed it — respond

    Remove basic-validator-pro 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 basic-validator-pro 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 basic-validator-pro 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. basic-validator-pro on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jxh6-q3x4-j7pfRLMA-2025-04925RLUA-2026-01117

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks basic-validator-pro-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

basic-validator-pro (npm) malicious package — MAL-2025-47175 | O3 Security