eslint-plugin-i18n-shreddit
This report shows the evidence for eslint-plugin-i18n-shreddit@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 1mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-16437 confirms this npm version as malicious.
Advisory
MAL-2026-16437
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in eslint-plugin-i18n-shreddit (npm)
Details
eslint-plugin-i18n-shreddit@99.9.9 ships no ESLint plugin code; the tarball's only function is a postinstall hook (scripts.postinstall = 'node index.js') that runs automatically on `npm install`. index.js collects installer-side reconnaissance — os.userInfo().username, process.cwd(), os.hostname(), and the local IPv4 address — and POSTs the values as JSON to a hardcoded anonymous collector at https://webhook.site/f9bff304-3053-4d54-be05-86537267514a. Package metadata is characteristic of a dependency-confusion probe: version 99.9.9 (chosen to win resolution against a lower-versioned internal package of the same name), empty description, empty author, and no exported plugin functionality. Installing this package leaks the installer's identifiers and network position to an attacker-controlled webhook, identifying vulnerable internal build environments for follow-on targeting.
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 eslint-plugin-i18n-shreddit@99.9.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing eslint-plugin-i18n-shreddit@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.