react-load-preact-example@0.0.0-stage
Malicious code in react-load-preact-example (npm)
Analysis
This release of react-load-preact-example (version 0.0.0-stage) ships no executable code. The tarball contains only package.json and README.md: the manifest contains no scripts, no bin entries, no dependencies and sets "stub": true with the description "Temporary package placeholder for staged publishing", and the README states it is a "Temporary Holding Version" with an "operational version" awaiting a staged release. Nothing in this version installs or runs. The release is a name-retention placeholder published under a package name whose earlier versions carried malicious content. It re-claims the name with a fresh latest tag while advertising that a functional version is coming, which is the staging shape used to keep a package name live and under one publisher's control before the real payload is swapped in. This advisory is metadata-only for this version: there is no payload, no lifecycle hook, no network destination, no credential access and no host artefact to report, because the tarball has none. Concrete indicators must be taken from the earlier malicious versions of this package, not from 0.0.0-stage. No network IOC exists in this tarball.
- analyzed by
- Leitwacht
- first seen
- Nov 11, 2026, 03:35 AM
- analyzed
- Nov 11, 2026, 03:38 AM
- weekly installs
- 59
Related advisories
- @swirls/cli@0.1.148
- @risacakep/risayap@7.0.0-rc25.14
- @risacakep/risayap@7.0.0-rc25.13
- @risacakep/risayap@7.0.0-rc25.6
- badbunny@0.0.0-stage
- sauruspro-bail@5.3.1
- @charape/baileys@1.0.7
- @trashcore/baileys@4.2.2
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.