Malicious code in @pwaplatform/module-sso-integration (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-16299
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4f674867f67f5a8495dbc953913b6cc7c0d8b9d094161c660ca4dfd5449506ba) @pwaplatform/[email protected] declares both preinstall and postinstall lifecycle scripts that execute payload.js on npm install. payload.js collects hostname, whoami, id, uname -a, the contents of /etc/passwd (up to 4096 bytes), cwd, INIT_CWD, the installing project's git remote and branch, its package.json metadata and top-level dependencies, npm config, CI environment variables, and node/platform information, base64/base64url-encodes the payload, and transmits it over plain HTTP to three hardcoded destinations: http://sobaka-kusaka.ru:8000/oob/<token>, http://sobaka-kusaka.ru:8898/c/<token>, and a Burp Collaborator subdomain at http://ii473egh1b4kbaw03rf7pkzik9q0er8fx.oastify.com/<token>. The @pwaplatform scope name, the implausibly high 99.0.1 version, and the out-of-band collaborator channel are consistent with a dependency-confusion attack against an internal scope; the README's 'authorized bug bounty canary' framing is author-controlled and does not reflect installer consent. ## Source: ghsa-malware (01c4bd1c4a83c7fac6d1b8aa7bd3e38639a7413a5d1fdd1d484b5c3e1dcb5341) 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. ## Source: ossf-package-analysis (774cfab0bd1150e7f7e40819176562e4e19983d87b347f5a55a0b60dfbbca7d3) The OpenSSF Package Analysis project identified '@pwaplatform/module-sso-integration' @ 99.0.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.
- Source published
- 20 Sep 2026 11:05:51 UTC
- Source modified
- 22 Sep 2026 18:45:06 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.