NullReceiver abandons the recording address that made EtherHiding easy to detect

cryptonews.ruPubblicato 2026-08-13Pubblicato ultima volta 2026-08-13

Introduzione

**Sonatype Research Labs has uncovered six malicious npm packages that retrieve command-and-control server addresses from an attacker's Ethereum wallet.** Three of the packages are legitimate, popular libraries that were compromised: `@kolbo/mcp`, `agentgui`, and `godot-kit`. The other three are purely malicious packages: `envpack-conf`, `postcss-initial-provider`, and `tailwindcss-motion-advanced`. All six deploy the same payload. The malware loader queries the Ethereum blockchain for the latest outgoing transaction from a specific wallet. It extracts bytes from the recipient field of that transaction, converts them into two IPv4 addresses, and uses these as primary and backup command-and-control servers. After connecting, it fetches, decodes, and executes a second-stage payload using `eval()` or by spawning a child process. This method, dubbed **"NullReceiver,"** is an evolution of the earlier "EtherHiding" technique. While EtherHiding hid data in transaction fields and sent funds to a fixed "burner" address (creating a monitoring point), NullReceiver sends no funds and generates unique, dynamic receiver addresses, making detection harder. OpenSourceMalware has linked this activity to the North Korean Lazarus group's "Contagious Interview" campaign. Sonatype advises developers to remove the affected package versions immediately and check their systems for signs of secondary payload execution.

Sonatype Research Labs published research findings showing that six npm packages retrieve their command-and-control server addresses from an attacker's Ethereum wallet.

Three of the six npm packages were well-known libraries that attackers stealthily hijacked. Anyone who installed the affected versions should remove them and check for any subsequent code that may have been executed.

Attackers hijacked three genuine libraries

Sonatype researcher Adam Reynolds says the six packages can be divided into two categories.

It appears that the publishing accounts of legitimate library publishers were compromised to facilitate the distribution of counterfeit versions.

These are @kolbo/mcp@1.57.1, agentgui@1.0.1127, and godot-kit@1.0.1786316795. They inserted a loader at the end of a file that was already part of the package, thereby preserving the original functionality.

The remaining three were purpose-built packages for malware distribution. These are envpack-conf@1.0.1, postcss-initial-provider@3.0.4, and tailwindcss-motion-advanced@1.0.1.

The first package contains configuration utilities, the second is a functioning PostCSS plugin, and the last package places the loader in a minified helper file.

Sonatype confirmed that all six code blocks use the same payload and Ethereum address.

When a victim runs the code, the loader queries Ethereum for information about the wallet's latest outgoing transaction and extracts bytes from the 'to' field of that transaction.

These bytes are converted into two IPv4 addresses. They serve as the primary and backup command-and-control servers for the malware. The transaction is used solely to store instructions on where the malware should connect.

Sonatype researchers stated the loader concurrently accesses multiple Ethereum endpoints and races them against each other. It then bundles its JSON-RPC requests and switches to the Blockscout API if direct requests fail.

After discovering the server, it makes two more attempts at the `/0x/cls` and `/0x/ls` endpoints, falling back to the `X-Payload-B64` response header if a regular GET request yields no result.

The returned result is Base64 and XOR decoded, then executed in the current Node.js process via the `eval()` function or launched as a separate child process.

NullReceiver is a more compact version of EtherHiding

This blockchain data retrieval scheme was discovered by OpenSourceMalware in two trojanized Tailwind CSS clones, bianira-ui and fluid-type-ui, and named NullReceiver.

The firm links this activity to the North Korea-linked "Contagious Interview" campaign and the Lazarus group. Sonatype confirmed a match in the wallet address.

NullReceiver removes a vulnerability in EtherHiding—a method which, according to Google Threat Intelligence, was developed by a North Korea-linked actor in October 2025.

EtherHiding hides a secret within a transaction's data field and always sends the transaction to a public Ethereum burn address, giving defenders a fixed point for monitoring.

NullReceiver does not send any data and does not reuse the destination. In the deconstructed OpenSourceMalware code snippet, the recipient bytes were identified as value 166.88.134.62, and the trailing bytes formed the string "helloipbot!!", which is the attacker's fingerprint.

In September 2025, Cryptopolitan reported that ReversingLabs discovered npm loaders colortoolv2 and mimelib2, which hid malware URLs inside Ethereum smart contracts linked to Stargazer's Ghost Network.

Sonatype stated it continues to investigate the related npm activity. Affected developers should remove the flagged npm packages. They should also watch for signs of second-stage payload execution.

end-content

Domande pertinenti

QWhat is the main vulnerability that NullReceiver addresses compared to the previous EtherHiding method?

ANullReceiver eliminates a key vulnerability in EtherHiding. EtherHiding always sent data to a public Ethereum burn address, providing defenders with a fixed point to monitor. NullReceiver sends no data and does not reuse a destination address, making it harder to detect.

QAccording to the article, how do the malicious npm packages retrieve their command and control server addresses?

AWhen the malicious code runs, it queries the Ethereum blockchain for the latest outgoing transaction from the attacker's wallet. It extracts specific bytes from the 'recipient' field of that transaction, which are then converted into two IPv4 addresses. These serve as the primary and backup command and control servers.

QWhat are the two categories into which the six identified malicious npm packages can be divided?

AThe six malicious npm packages fall into two categories. Three are legitimate libraries (like @kolbo/mcp) whose publishing accounts were compromised to distribute a trojanized version. The other three are purpose-built malicious packages (like envpack-conf) specifically created to distribute malware.

QWhich cybersecurity firm linked the NullReceiver activity to the North Korean 'Contagious Interview' campaign and the Lazarus group?

AThe cybersecurity firm OpenSourceMalware linked the NullReceiver activity to the North Korean 'Contagious Interview' campaign associated with the Lazarus group. Sonatype confirmed a match in the wallet data, supporting this attribution.

QWhat should developers who installed the affected npm package versions do, according to the article's recommendations?

ADevelopers who installed the affected versions should remove those npm packages immediately. They should also check their systems for any signs of second-stage payload execution that might have occurred as a result of the initial infection.

Letture associate

Trezor Customer Data Leak: Coins Are Safe, But Phishing Is Inevitable

Trezor, a hardware cryptocurrency wallet manufacturer, reported a data breach at its logistics partner, ShipMonk, affecting around 13,689 customers. The incident, confirmed on August 13, 2026, involved unauthorized access to ShipMonk's systems, which stored order information from May 10 to August 8, 2026. Trezor's own systems and user crypto assets were not compromised. The leaked data varies: for 11,742 customers, full names, email addresses, phone numbers, and delivery addresses were exposed. For 1,947 others, only name, city, and email were leaked. The breach was limited to customers in the US, UK, Sweden, Colombia, Brazil, Italy, and Portugal. Trezor warns affected users of an increased risk of phishing attacks, where malicious actors may use the stolen contact details to impersonate Trezor, banks, or exchanges to steal wallet recovery phrases. All impacted customers have been notified via email. In response, Trezor announced a planned "Anonymous Delivery" feature for the EU (September 2026) and the US (end of 2026), aiming to anonymize logistics data. ShipMonk has not yet issued a public statement on its official website. The analysis highlights this as a recurring industry pattern where third-party logistics vendors become weak links in the supply chain, storing data longer than necessary. Similar incidents, like the 2020 Ledger breach, led to prolonged phishing campaigns. A key question remains whether hardware wallets can ever fully decouple from external logistics risks.

cryptonews.ru7 min fa

Trezor Customer Data Leak: Coins Are Safe, But Phishing Is Inevitable

cryptonews.ru7 min fa

Token Buyback Volumes Continue to Rise, But Price Lows Keep Falling

The volume of token buybacks continues to grow, but the minimum price level is constantly declining, according to an internal memo by Bitwise CIO Matt Hogan. He argues that most crypto tokens, except Bitcoin, are undervalued as investors are unaware of the revenue now being returned to holders. He highlights the example of Hyperliquid, which has bought back and burned $1.3 billion worth of its $HYPE token. Hogan posits that tokens are beginning to trade based on revenue, similar to stocks and bonds, marking the end of an era where scaling networks provided little token utility. He links token valuation to strengthening protocol revenue, noting that Hyperliquid has earned over $800 million in the past year and spends nearly all fees on $HYPE buybacks. Following this model, protocols like Uniswap and Aave have implemented fee mechanisms to buy back and burn their own tokens. The trend has also affected base chains like Solana and Aptos, which have proposed or enacted higher fee burns. However, the memo acknowledges that reducing token supply has not reliably boosted prices. A Cryptopolitan report found many tokens with regular buybacks still underperformed the market. Even Hyperliquid's upward trend broke, and Pump.fun conducted significant buybacks near token lows. Hogan cautions that token buybacks differ from stock buybacks due to the lack of contractual claims on profits or assets, as governance rules can always be rewritten.

cryptonews.ru57 min fa

Token Buyback Volumes Continue to Rise, But Price Lows Keep Falling

cryptonews.ru57 min fa

Trading

Spot
活动图片