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

The following npm versions of @nativescript-community/sqlite are flagged malicious: 3.5.2, 3.5.3, 3.5.4, 3.5.5. Treat any of these as compromised.

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

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

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

Yes — @nativescript-community/sqlite is associated with the GHSA-ffh4-vmhf-h766 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/sqlite 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/sqlite (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/sqlite across your stack and pipelines.

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

Malicious package

@nativescript-community/sqlitenpm

@nativescript-community/sqlite is a confirmed malicious npm package (MAL-2025-47150) that steals credentials and exfiltrates sensitive data (malicious versions 3.5.2, 3.5.3, 3.5.4…). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2025-47150

Immediate action

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

npm uninstall @nativescript-community/sqlite

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

3.5.23.5.33.5.43.5.5

Indicators of compromise (SHA-256)

12fdec6c515865f33dafbfd89c6a2e810138eab46fe92d29955d74a13e37567f

43cc8bc8a66fbb0a3340be7abd567ed769e027aa6ee2812b00665060b666230a

2aa9ea337f7476f4c71bdcad9373173580ff8a1cc50ebab93d6608eddaab755e

72ba187da5513210161e9baf5b6e38399976fd7ce74a7cf77cc03c10e74d19d6

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/sqlite (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/sqlite across your stack and pipelines.
If you installed it — respond
@nativescript-community/sqlite 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/sqlite 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/sqlite 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/sqlite on npm has been identified as a malicious package (versions 3.5.2, 3.5.3, 3.5.4, 3.5.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-ffh4-vmhf-h766

References

Detect & block this

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