Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @nativescript-community published 20 malicious packages. See the full campaign →
Malicious package

@nativescript-community/ui-material-ripplenpm

@nativescript-community/ui-material-ripple is a confirmed malicious npm package (MAL-2025-47390) that steals credentials and exfiltrates sensitive data (malicious versions 7.2.72, 7.2.73, 7.2.74…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @nativescript-community/ui-material-ripple (npm)

MAL-2025-47390
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @nativescript-community/ui-material-ripple

What this malware does

The package was compromised and malicious code added.

This package was compromised by the Shai-Hulud NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub before propogating itself to NPM packages the user owns.

Malicious versions

4 flagged
7.2.727.2.737.2.747.2.75

Indicators of compromise (SHA-256)

98bc88d841f7cc3ff226e714214d8710303b66e19159e2672746eedc0d7a5c0e

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    @nativescript-community/ui-material-ripple is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @nativescript-community/ui-material-ripple 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 @nativescript-community/ui-material-ripple 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. @nativescript-community/ui-material-ripple on npm has been identified as a malicious package (versions 7.2.72, 7.2.73, 7.2.74, 7.2.75 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @nativescript-community/ui-material-ripple-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@nativescript-community/ui-material-ripple (npm) malicious package — MAL-2025-47390 | O3 Security