Malicious code in @ppa-web-components/ppa-hotel-collection (npm)
Published Sources: OSV (Schadpakete)
- Malicious package
What is affected, what to do
Uninstall the package, isolate affected environments and rotate credentials that were available during installation.
Not sure whether and how you are affected? Ask a question about this vulnerability
Malicious package
npm@ppa-web-components/ppa-hotel-collection
“@ppa-web-components/ppa-hotel-collection” is registered as malicious in the npm repository. Anyone who installed the package should uninstall it immediately, isolate affected environments and rotate credentials that were present during installation.
Affected versions (7)
- 0.0.0-stage
- 0.1.0
- 1.0.0
- 1.1.0
- 2.0.1
- 3.0.0
- 99.0.1
purl: pkg:npm/%40ppa-web-components/ppa-hotel-collection
Sources (8)
amazon-inspector
IN-MAL-2026-021655Versions from this source: 99.0.1
sha256: 79c01e5cd9accbd2f679b11f151a03bfb2793a50490ae9a97f8ebfd6515e5eb6
amazon-inspector
IN-MAL-2026-021651Versions from this source: 1.1.0
sha256: e442008a433c1edbe8fb25f9b47dd3123f5664672c3901167fc9d3add8a6bd6e
amazon-inspector
IN-MAL-2026-021652Versions from this source: 3.0.0
sha256: 90e1177495a62104fc3642faacfc70682252b925c35632673e6357b844748791
amazon-inspector
IN-MAL-2026-021653Versions from this source: 1.0.0
sha256: a086f064036e6d43268ce3396ae6068a3ac9e2f2fa7f1636f64039b88864ba98
amazon-inspector
IN-MAL-2026-021650Versions from this source: 2.0.1
sha256: d5157f4c405a682213856c9849e643365295e3b95a7a2288dbc3b512960eb247
ghsa-malware
GHSA-4p22-gg56-8457sha256: 5c6c67a20abb37db21d16508f031264290a06f2426dc6cb70f74cc3f5d73d3a1
amazon-inspector
IN-MAL-2026-022141Versions from this source: 0.0.0-stage
sha256: 4fe34628d4d2f1feac2400050bfd1da719c889ddc11ad34de68855ccc2bd8da1
amazon-inspector
IN-MAL-2026-022289Versions from this source: 0.1.0
sha256: 99194d255042cdbade246ec8446385a7e882a103d4aaba751ff94dd25656c32e
The OSSF `malicious-packages` namespace lists packages flagged as malicious by static analysis or sandbox detonation. An entry here is a confirmed finding, not a suspicion.
Metrics
—
Priority
No value is available for this vulnerability.
—
CVSS v3
No value is available for this vulnerability.
—
EPSS score
No value is available for this vulnerability.
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 30.00 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
@ppa-web-components/ppa-hotel-collection is a dependency-confusion package: it is described as a "Compatibility shim", uses inflated version numbers, and its README calls it an "authorized dependency-confusion test". Each listed version (1.1.0, 1.0.0, 99.0.1, 2.0.1, 3.0.0) has a postinstall script that runs node beacon.cjs on npm install, and index.js calls the same code when the package is imported; it POSTs the hostname, install path and current working directory over plain HTTP to http://185.158.107.175:8787/_ah/dc, and index.js exports a Proxy that returns no-op functions so builds importing the real package keep running. The npm account wiseke published 14 such packages under the @greenlake, @sxm-web, @drone-js-ext and @ppa-web-components scopes between 2026-10-23 21:23 and 2026-10-25 14:28 UTC; index.js is byte-identical to that of ph-common (MAL-2026-1809), which sends to the same endpoint.
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (e442008a433c1edbe8fb25f9b47dd3123f5664672c3901167fc9d3add8a6bd6e)
@ppa-web-components/ppa-hotel-collection@1.1.0 is a stub package whose only functional code is a callback beacon. The package.json declares scripts.postinstall: "node beacon.cjs", and the same beacon.cjs is also triggered via the main entry on require(). beacon.cjs collects os.hostname(), __dirname, process.cwd(), and process.version/npm version and POSTs them to the hardcoded bare-IP URL http://185.158.107.175:8787/_ah/dc over cleartext HTTP. The destination is unrelated to any legitimate publisher infrastructure for the @ppa-web-components scope. The package's only export is a no-op Proxy, and the description self-labels as "Compatibility shim." with internal comments noting that a build which "completes and calls back is cleaner evidence" — consistent with a dependency-confusion probe targeting an internal @ppa-web-components namespace. Installing or requiring the package automatically exfiltrates host and path identifiers to attacker-controlled infrastructure, marking the installer's build system as reachable for follow-on targeting.
Source: ghsa-malware (5c6c67a20abb37db21d16508f031264290a06f2426dc6cb70f74cc3f5d73d3a1)
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 installing it.