A cross-site scripting (XSS) vulnerability exists in the yahoo serialize-javascript library prior to version 7.1.3. The flaw arises because the function-source escaping logic fails to neutralize a bare closing-script prefix when attacker-controlled function source text ends exactly at that prefix. This can allow an attacker who controls a serialized function's source text to inject malicious markup that becomes live in the page. The issue is fixed in version 7.1.3.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (42d10ba1427af01794dfb0a6b39a05f969547455e9d86d75f18601b1d035c507)
preinstall.js runs unconditionally on npm install and POSTs a JSON payload to a hardcoded Pipedream collector at https://f5778d1d81cc30c39dcdd0da5ca1d49a.m.pipedream.net. The payload includes os.hostname(), os.userInfo() username, platform/arch/node version, process.env.INIT_CWD, process.cwd(), the consumer project's package.json name and version, whether the consumer declares an @alphaspace dependency, npm registry hosts parsed from ~/.npmrc, CI-related environment variable names, and proxy host configuration. The same script performs DNS resolution against a hardcoded list of *.yahoo.com and *.ouryahoo.com internal hostnames (including istio-system.prod1-gq1.omega.yahoo.com and buildr.corp.yahoo.com), and for any banana.stand.*.yahoo.com name that resolves it issues an https.request with rejectUnauthorized:false, capturing the response status, Server header, and first 512 bytes of the body and forwarding them in a banana_proof field of the exfil payload. The @alphaspace scope name and an in-file 'authorized security research' banner form a dependency-confusion lure aimed at Yahoo internal builds; the installer-side behavior — host fingerprinting, npmrc/registry disclosure, and TLS-verification-disabled internal-network probing from the installer's host — fires against any machine that resolves this package.
SearchJack represents a coordinated campaign comprising 23 deceptive Chrome browser extensions that silently hijack users' default search engines, redirecting queries through monetization middleware before delivering results. These extensions masquerade as various productivity tools, satellite imagery viewers, maps, and news readers while their actual purpose is generating search affiliate revenue. The campaign affects approximately 758,000 users across 22 unique publishers and leverages at least 8 distinct monetization brokers, primarily routing traffic through Yahoo Hosted Search affiliate programs. The extensions employ manifest-only wrappers using chrome_settings_overrides to hijack search settings, with some implementing runtime obfuscation to evade static analysis. Several extensions feature false privacy claims, anomalous review patterns, and anonymous publishers with fictional corporate identities, enabling operators to monetize user search behavior while maintaining zero accountability.
Microsoft has implemented enforcement of DMARC policies for outbound email sent to its consumer email services (Outlook.com, Hotmail.com, Live.com) starting May 5, 2025. Domains sending 5,000 or more messages per day must have properly configured SPF, DKIM, and DMARC records with domain alignment to avoid silent rejection of their emails. Messages failing these authentication checks are rejected without bounce or notification, causing potential silent delivery failures. This enforcement primarily affects bulk mailers such as newsletters and transactional email services. Microsoft 365 business accounts use a different filtering system and are not impacted by this policy. The enforcement aligns Microsoft with other major providers like Google and Yahoo, who adopted similar policies earlier. Domains lacking these DNS records or with misconfigurations risk losing email deliverability to Microsoft consumer inboxes.
Improper authorization in handler for custom URL scheme issue in "Yahoo! Shopping" App for Android versions prior to 14.15.0 allows a remote unauthenticated attacker may lead a user to access an arbitrary website on the vulnerable App. As a result, the user may become a victim of a phishing attack.