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

The following npm versions of @nativescript-community/typeorm are flagged malicious: 0.2.30, 0.2.31, 0.2.32, 0.2.33. Treat any of these as compromised.

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

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

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

Yes — @nativescript-community/typeorm is associated with the GHSA-6pxr-2g69-7q3v 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/typeorm 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/typeorm (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/typeorm across your stack and pipelines.

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

Malicious package

@nativescript-community/typeormnpm

@nativescript-community/typeorm is a confirmed malicious npm package (MAL-2025-47152) that steals credentials and exfiltrates sensitive data (malicious versions 0.2.30, 0.2.31, 0.2.32…). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2025-47152

Immediate action

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

npm uninstall @nativescript-community/typeorm

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

0.2.300.2.310.2.320.2.33

Indicators of compromise (SHA-256)

6f52d32f97f0c022f47383943d101a89ef5465d96aece46233bc2005a4c14d6a

f7a494563257838e7b30eeb0479c911d9a9fa8f2c2940c2f6726e0bf16cef15e

6affca002f9d3fee9b70b601766467ef2ca9cee4905164872e58d7d95e9f00e4

4fb1e194a26415b04af4e6c26f718273fa27cb72fca8f42e0d12fde14ca445b1

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

Campaign

GHSA-6pxr-2g69-7q3v

References

Detect & block this

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