Which versions of react-native-get-pixel-dimensions are malicious?

The following npm versions of react-native-get-pixel-dimensions are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate react-native-get-pixel-dimensions if I installed it?

react-native-get-pixel-dimensions 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 react-native-get-pixel-dimensions — how do I know if it already compromised me?

If react-native-get-pixel-dimensions 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 react-native-get-pixel-dimensions part of a known attack campaign?

Yes — react-native-get-pixel-dimensions is associated with the GHSA-pc7r-3qqx-jjrv 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 react-native-get-pixel-dimensions 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 react-native-get-pixel-dimensions (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-native-get-pixel-dimensions across your stack and pipelines.

Malicious package

react-native-get-pixel-dimensionsnpm

Malicious code in react-native-get-pixel-dimensions (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190998

Immediate action

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

npm uninstall react-native-get-pixel-dimensions

What this malware does

The package react-native-get-pixel-dimensions was found to contain malicious code.

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 Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

c33b23d6a460a044d3be46c1adb9dd5b825b4c80e43aa67a95a1f2854edfde3e

d3570e34574e0faad44ff9473f62241285d926a86915d14b3593b9c3105520fc

e6f983cd17eac3ccab99cc8e719737a9bb7c6c1143ce80f6bcb86e1f9c297d55

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 react-native-get-pixel-dimensions (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-native-get-pixel-dimensions across your stack and pipelines.
If you installed it — respond
react-native-get-pixel-dimensions 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 react-native-get-pixel-dimensions 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 react-native-get-pixel-dimensions 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. react-native-get-pixel-dimensions on npm has been identified as a malicious package (versions 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pc7r-3qqx-jjrv

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks react-native-get-pixel-dimensions-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