Which versions of @nativescript-community/sentry are malicious?

The following npm versions of @nativescript-community/sentry are flagged malicious: 4.6.43. Treat any of these as compromised.

How do I remediate @nativescript-community/sentry if I installed it?

@nativescript-community/sentry 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.

I already installed @nativescript-community/sentry — how do I know if it already compromised me?

If @nativescript-community/sentry 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.

Is @nativescript-community/sentry part of a known attack campaign?

Yes — @nativescript-community/sentry is associated with the GHSA-5wmf-c85p-rxv6 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @nativescript-community/sentry across my projects, lockfiles, and CI pipelines?

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

Part of a larger attack: @nativescript-community published 20 malicious packages. See the full campaign →

Malicious package

@nativescript-community/sentrynpm

@nativescript-community/sentry is a confirmed malicious npm package (MAL-2025-47149) that steals credentials and exfiltrates sensitive data (malicious version 4.6.43). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @nativescript-community/sentry (npm)

MAL-2025-47149

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @nativescript-community/sentry

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

1 flagged

4.6.43

Indicators of compromise (SHA-256)

ac70fd6ee04f2650c317de593d4341b084f7a1564e4bf36fed85c72971ce9878

0e9af28a4a827c0aab33232985b306c64e451d88be93de98adcddb1fcb70c807

89be65554426fb76b734d478d74bccc5dbc99899a3f7e7aede1a7889c3467acd

c59a66020a6f63e8f250036f1b64a3e19c6ff6dddc9fa0e41192990c7c10eac4

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @nativescript-community/sentry (version 4.6.43). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nativescript-community/sentry across your stack and pipelines.
If you installed it — respond
@nativescript-community/sentry 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.
Did it already run?
If @nativescript-community/sentry 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.
How O3 protects you
O3 blocks @nativescript-community/sentry 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/sentry on npm has been identified as a malicious package (version 4.6.43 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5wmf-c85p-rxv6

References

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database