@goparrot-dashboard/franchise-directory
This report shows the evidence for @goparrot-dashboard/franchise-directory@0.0.1, the only known version.
OpenSSF/OSV Malicious Advisory
imported 2d ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-18498 confirms this npm version as malicious.
Advisory
MAL-2026-18498
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @goparrot-dashboard/franchise-directory (npm)
Details
@goparrot-dashboard/franchise-directory is a dependency-confusion probe: it takes a name in a `@goparrot-dashboard` scope that its publisher created on npm, next to GoParrot's public `@goparrot` scope, so a build that resolves that scope from npm gets it instead of a private package of the same name. Version 0.0.1 has no install scripts, and its `index.js` only prints a "[rootxravi-poc-security] @goparrot-dashboard/franchise-directory" marker when loaded. The npm account devtest91001 published it on 2026-11-01 with 24 other packages in `@goparrot-dashboard` and `@goparrot-dashboard-api`, including @goparrot-dashboard/app, whose 0.0.2 sends the hostname, user and working directory to an interactsh callback host (`iuczektmwpudhwqnsbkgc6m8nx2dgn5vc.oast.fun`) from a preinstall script.
References
Independent scan evidence
public snapshotBehavioral surface
Trivial
Source & flagged code
0 flaggedNo flagged code excerpts are attached to this scan.
Findings
0No findings.
Affected versions and remediation
This report applies to @goparrot-dashboard/franchise-directory@0.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @goparrot-dashboard/franchise-directory@0.0.1. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.