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

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

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

@nativescript-community/gesturehandler 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/gesturehandler — how do I know if it already compromised me?

If @nativescript-community/gesturehandler 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/gesturehandler part of a known attack campaign?

Yes — @nativescript-community/gesturehandler is associated with the GHSA-xffh-x5wf-63g4 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/gesturehandler 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/gesturehandler (version 2.0.35). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nativescript-community/gesturehandler across your stack and pipelines.

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

Malicious package

@nativescript-community/gesturehandlernpm

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

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

MAL-2025-47147

Immediate action

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

npm uninstall @nativescript-community/gesturehandler

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

2.0.35

Indicators of compromise (SHA-256)

1c25d691508dd5a2da24859854f28998b2bc0456d3e73edfc5aeeb61c2fd7d1a

88f7b49093224f4502c46850260e79e686e499a5ddac0e322c92f8580933d78c

5507f68c7aec3a86f4f106e103558d56ab8722fcb55a7766a60b089a5dc109fd

afe37ce0112d205ec0765d171706aa4b80a25d5588cd2665fe85e03ca7d53bc8

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/gesturehandler (version 2.0.35). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nativescript-community/gesturehandler across your stack and pipelines.
If you installed it — respond
@nativescript-community/gesturehandler 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/gesturehandler 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/gesturehandler 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/gesturehandler on npm has been identified as a malicious package (version 2.0.35 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xffh-x5wf-63g4

References

Detect & block this

O3 blocks @nativescript-community/gesturehandler-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