Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in post-css-transfer (npm)

Exploitation and risk

Source status

CISA 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-12417

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f62ccc235772a34a28d870f349489698c167e3d636a196f310fe24c1ce1d4ef4) post-css-transfer is a typosquat of postcss whose main entry lib/postcss.js has an obfuscated IIFE appended after the legitimate module code. On require/import, the appended block resolves a command-and-control IP by reading transactions of Ethereum address 0xa322E5f3D311D3080e6f0121063e9aDC2490Ef1a via public Ethereum RPC endpoints and the eth.blockscout.com API, decodes two IPv4 addresses from the transaction recipient bytes, fetches an XOR-encrypted payload over HTTP from those hosts (delivered in an x-payload-b64 header), and executes the decrypted payload via eval() and a detached `node -e` child process. Network, execution, and identifier primitives (http, child_process, spawn, the Ethereum address, method and header names) are written as \uXXXX escapes and hidden behind ~1KB of whitespace padding after `module.exports = postcss;` to evade casual review. ## Source: ghsa-malware (3e35af1cb71e17048626ceebf0ea0022262f7bfbbfd82cedf4c9ee5c19bfaa76) 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 published
5 Aug 2026 12:46:11 UTC
Source modified
11 Aug 2026 00:50:17 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.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 09:08 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current