@webapp-next/store
This report shows the evidence for @webapp-next/store@91.1.0, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-3749 confirms this npm version as malicious.
Advisory
MAL-2026-3749
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @webapp-next/store (npm)
Details
package.json declares "preinstall": "node index.js", which runs automatically on npm install. index.js collects os.hostname(), os.platform(), os.arch(), os.homedir(), os.userInfo() (username, uid, gid, shell), OS release/memory/CPU info, process.cwd(), and the output of shell commands `whoami` and `id`, then POSTs the aggregated JSON to https://oia2jeijtfmt053ynp686t5riioac00p.oastify.com/testbydext. The destination is a Burp Suite Collaborator out-of-band interaction subdomain controlled by the attacker. The package has no legitimate functionality — index.js contains only the exfiltration payload, and package.json carries empty author/description fields under a scope (@webapp-next) that resembles a legitimate namespace, consistent with a dependency-confusion lure.
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 @webapp-next/store@91.1.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @webapp-next/store@91.1.0. 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.