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

@nstudio/nativescript-checkboxnpm

@nstudio/nativescript-checkbox is a confirmed malicious npm package (MAL-2025-47164) that steals credentials and exfiltrates sensitive data (malicious versions 2.0.6, 2.0.7, 2.0.8…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @nstudio/nativescript-checkbox (npm)

MAL-2025-47164
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @nstudio/nativescript-checkbox

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.

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
2.0.62.0.72.0.82.0.9

Indicators of compromise (SHA-256)

6ac10be560243885c47e80e47d545e8006f285d8fe9f5756c7b92f9cd2085639
42f1d4c33f745431f51c01ce03da9d81547e76e13b1433163f4ddd6ea8f49593
7dc3708147e4bb8ccc5f159a64800fc614fddecaba4344de6247fbb14e3544b4
13a088ac026b6ad8455acb3cd5af16d79820e5219a8a32c54379f4b1780f7e5c

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 @nstudio/nativescript-checkbox (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nstudio/nativescript-checkbox across your stack and pipelines.

  2. If you installed it — respond

    @nstudio/nativescript-checkbox 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 @nstudio/nativescript-checkbox 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 @nstudio/nativescript-checkbox 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. @nstudio/nativescript-checkbox on npm has been identified as a malicious package (versions 2.0.6, 2.0.7, 2.0.8, 2.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-8cm7-6wjr-9qcf

References

Detect & block this

O3 blocks @nstudio/nativescript-checkbox-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

@nstudio/nativescript-checkbox (npm) malicious package — MAL-2025-47164 | O3 Security