What does the rn-push-provisioning malware do?

The package's package.json declares a preinstall lifecycle script (`node beacon.js || true`) that runs automatically during `npm install`. beacon.js reads os.hostname(), os.userInfo().username, process.platform, and process.arch and sends them via https.get to the hardcoded endpoint https://m3p49wwj8ttzz98h.datasafeservices.com/npm-install? . The package is published at version 99.0.0 with a name consistent with a dependency-confusion lure targeting installers who resolve an internal name to the public registry. Collected identifiers fingerprint the installer's host and user account and are transmitted to a third-party subdomain unrelated to any documented publisher, satisfying the ins

Which versions of rn-push-provisioning are malicious?

The following npm versions of rn-push-provisioning are flagged malicious: 99.0.0, 99.0.1. Treat any of these as compromised.

How do I remediate rn-push-provisioning if I installed it?

rn-push-provisioning 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 rn-push-provisioning — how do I know if it already compromised me?

If rn-push-provisioning was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is rn-push-provisioning part of a known attack campaign?

Yes — rn-push-provisioning is associated with the GHSA-mjgw-fv57-pvwm, IN-MAL-2026-018813, IN-MAL-2026-018814 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 rn-push-provisioning across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for rn-push-provisioning (2 malicious versions).

Malicious package

rn-push-provisioningnpm

Advisory published Aug 27, 2026Updated Aug 28, 2026

rn-push-provisioning is a confirmed malicious npm package (MAL-2026-14563) that steals credentials and exfiltrates sensitive data (malicious versions 99.0.0, 99.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rn-push-provisioning (npm)

MAL-2026-14563

Immediate action

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

npm uninstall rn-push-provisioning

What this malware does

The package's package.json declares a preinstall lifecycle script (node beacon.js || true) that runs automatically during npm install. beacon.js reads os.hostname(), os.userInfo().username, process.platform, and process.arch and sends them via https.get to the hardcoded endpoint https://m3p49wwj8ttzz98h.datasafeservices.com/npm-install?<query>. The package is published at version 99.0.0 with a name consistent with a dependency-confusion lure targeting installers who resolve an internal name to the public registry. Collected identifiers fingerprint the installer's host and user account and are transmitted to a third-party subdomain unrelated to any documented publisher, satisfying the install-time exfiltration fingerprint.

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.

Malicious versions

2 flagged

99.0.099.0.1

Indicators of compromise (SHA-256)

3123fbb2393a8b9bf74cadf91531791520b038c28e1f941c36b3d77f0511f449

0dcb3938b1f4cc0e97a2fa1677c812a5ee9cdfc982233ea04eab5bdfdf3bad1d

77239db1bdbbae9f987b93749d88f1ea172ac43523377e2a47a40a0e0177a023

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for rn-push-provisioning (2 malicious versions).
If you installed it — respond
rn-push-provisioning 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 rn-push-provisioning was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. rn-push-provisioning on npm has been identified as a malicious package (versions 99.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mjgw-fv57-pvwmIN-MAL-2026-018813IN-MAL-2026-018814

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks rn-push-provisioning-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