Malicious code in 789bet-vip (npm)
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm 789bet-vip
- Affected
- every version
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record MAL-2026-18386 lists affected ranges: npm 789bet-vip >=0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- not scored
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
--- _-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (4abb3e4b3a01fecb2b28af9d833cb422943367e8901fabd11cff9125ed891305) 789bet-vip@0.0.0-stage is a minimal npm package (2 files) with no install lifecycle scripts, no network activity, no credential access, and no executable logic observed in its contents. The package name suggests a promotional or placeholder registration rather than a functional library, and no code paths that would harm an installer are present.
Source: ghsa-malware (89f42dbd0e59f1a22fcf7bc79133a84da721ea78a4be37c6a0fe77775cf28c45) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record MAL-2026-18386
- Revision 1 · created ·
Published from osv record MAL-2026-18386
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-rvxc-82gp-xpr6 Advisory: Malicious code in 789bet-vip (npm) IDs: GHSA-rvxc-82gp-xpr6 Record: https://patchnext.com/advisories/mal-2026-18386 (revision 2, source checked 31 Oct 2026, 06:00 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Unrated Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm 789bet-vip: affected every version ## Suggested inspection (read-only) - `npm ls 789bet-vip --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on 789bet-vip. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/MAL-2026-18386 (OSV record MAL-2026-18386 lists affected ranges: npm 789bet-vip >=0) Commands are suggestions: review each one before running it.
Loading voting…