ronyfortest
This report shows the evidence for ronyfortest@99.9.9, the only known version.
This package appears in our research on the dependency confusion probes at version 99 and above, with how it works, the full package list and what to do if you installed it.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-7002 confirms this npm version as malicious.
Advisory
MAL-2026-7002
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in ronyfortest (npm)
Details
The package's postinstall hook (`node index.js`) runs automatically on `npm install` and collects the installer's OS username (`os.userInfo().username`), hostname (`os.hostname()`), and working directory (`process.env.INIT_CWD || process.cwd()`), then POSTs them as JSON to a hardcoded webhook.site inspector URL (https://webhook.site/49781ccd-e409-4a90-8a42-34ed52b9e7b1). package.json ships empty author/description/keywords metadata and declares no legitimate purpose. The behavior is an unconditional install-time beacon that leaks installer host/user identifiers to an author-controlled inspection endpoint.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to ronyfortest@99.9.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing ronyfortest@99.9.9. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.