The npm package 'rai6jaisahthaghee5ou-loader-package' version 1.0.0 contains malicious code that injects a script element pointing to an attacker-controlled URL. This causes arbitrary JavaScript from the external host to execute within the context of any application bundling this package, enabling full code execution, credential or session theft, and further malicious actions.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (37cd33c0908189c0085fba153be1c42776411968aa5ad652dd7ffdef88b318bc)
hardhat-zet@2.0.1 is published under a name that impersonates the Hardhat Ethereum tooling ecosystem, but its README, type definitions and docs/ tree are copied verbatim from the unrelated `pino` logger project (badges and links point at npmjs.com/package/pino and github.com/pinojs/pino). The exported `middleware` in index.js is a no-op Express middleware and matches neither the `hardhat-zet` name nor the pino README. The package's declared main (index.js) top-level-requires./lib/config, which is not a configuration file but a 4,498,609-byte obfuscator.io-style bundle: a 26,113-entry rotated string array behind two runtime decoders (functions v and F), hex-encoded identifiers, and control-flow flattening. All strings and destination URLs are hidden behind the decoders, so this code runs automatically on any `require('hardhat-zet')` and its behavior is not observable without deobfuscation. Publisher metadata (author 'Robert King <hello@jsonspack.com>', bugs URL https://jsonspack.com/issues) ties to neither the Hardhat nor the pino identity. The combination — ecosystem-typosquat name targeting crypto/Hardhat developers, cover-story README lifted from an unrelated popular package, no-op public API, and a multi-megabyte obfuscated payload auto-executed on import — is the shape of a supply-chain stealer aimed at Ethereum developers.
## Source: ghsa-malware (781273d2c802d3781fecccd4434ba418c93ce88edf920b2a1163dbacf7576254)
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.
The npm package hardhat-lock@2.21.0 is a malicious package that impersonates a legitimate logging/middleware library but contains a large, heavily obfuscated payload that executes immediately upon import. This payload grants attacker-controlled code unrestricted access to environment variables, filesystem, and network within the Node.js process. The package misuses the Ethereum tooling keyword 'hardhat' and copies unrelated project documentation to disguise its true nature.
The npm package mini-hardhat version 1.1.4 contains malicious code that masquerades as a JSON logger but actually spawns a detached child process. This child process fetches and executes remote code from an obfuscated URL, enabling arbitrary code execution within the user's Node.js environment. The malicious behavior is engineered to persist beyond the parent process, making it a remote code execution dropper.
The npm package native-env@1.0.1 is a malicious package masquerading as a zero-dependency dotenv toolkit. On Windows, it executes attacker-controlled code immediately upon being required or run. It uses a JPEG file as a payload carrier to evade static scanners, writes a VBScript to the temp directory, and launches a PowerShell command with an encoded payload. The package is a typosquatting attempt targeting dotenv-family packages.
The npm package dotenv-native (version 1.0.1) is a malicious typosquat of the popular dotenv package family. It executes attacker-controlled code on module load by extracting and decoding a hidden payload from a bundled JPEG file, writing a VBScript file, and launching PowerShell with an encoded command on Windows hosts. The package also includes an obfuscated decode-and-eval remote code execution primitive. Both requiring the package as a dependency or running its CLI triggers the malicious payload.
The npm package fabric-native-loader version 1.0.0 contains malicious code that executes during installation. It steals Minecraft launcher credentials and related tokens from various launcher files and system information, then sends this data to a hardcoded Discord webhook. The package does not provide any legitimate functionality matching its name and solely acts to exfiltrate sensitive user credentials.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (a8e49b1abd7c566b17104c5a2823251df2ca253a0fa509d7c19db1c1942ad13d)
On require, index.js invokes initializeDaemon() at top level, which uses spawn('node', [lib/check-items.js], { detached: true, stdio: 'ignore' }) followed by child.unref() to launch a persistent background process independent of the parent. The daemon HTTP-GETs a JSON payload from the hardcoded endpoint https://game.spawnrealm.com/api/item-realtime?key=abcdef123456 and passes payload.code to `new Function('require', 'module', payload.code)`, executing server-supplied JavaScript inside the installer's Node process with full `require` access. An RSA signature check is performed against a public key bundled in the package (crypto-config.js), so the author controls both the signing key and the verifier and the check provides no independent integrity guarantee. Anyone controlling game.spawnrealm.com — including via DNS or TLS — can run arbitrary code as the installing user for the lifetime of the host process. The package is advertised as a validator library, and this remote-code-loader behavior is undisclosed and unrelated to the stated purpose.
The npm package 'test-agency-assignment' version 1.0.2 contains malicious code that executes automatically on Windows hosts during installation. It uses a postinstall script to run a Visual Basic Script (VBS) that decrypts and loads a PowerShell payload designed for process hollowing, enabling arbitrary code execution. The package masquerades as a benign telemetry tool but functions solely as a dropper for attacker-controlled code.
The llm-nebula npm package version 1.0.0 contains a malicious preinstall script that executes automatically during installation. This script is heavily obfuscated and runs with the user's privileges, enabling arbitrary filesystem, process, and network operations. The package pretends to be a legitimate LLM SDK but includes a runtime decoder that dynamically resolves Node.js built-in modules and commands, allowing remote code execution at install time.
The npm package simple-date-formatter-new-12@1.0.0 contains malicious code in its postinstall script that executes automatically during installation. This script fetches data from an internal Baidu host and exfiltrates the response to an attacker-controlled server. The package's stated functionality is a simple date formatter, but the embedded network activity is unrelated and indicative of a dependency confusion or typosquatting attack to probe internal network access and leak data.
The nebulaai-sdk npm package version 1.0.0 contains malicious code that executes a hidden Windows executable during installation on Windows systems. This executable is disguised as a legitimate Windows console host binary and establishes a remote command-and-control connection. The package lacks legitimate SDK functionality and solely serves to deploy and run this malicious payload, resulting in arbitrary code execution under the installing user's context.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (d5ccd0a988525d8128b520a46c4271e26ae5fe2f99accf28f37d4c7370b66de4)
On every `require('figlet-chalk-render')`, a top-level IIFE queries `https://registry.npmjs.org/figlet-chalk-render/latest` and, if a newer version exists, spawns `npm install figlet-chalk-render@<latest>` with cwd set to `path.join(__dirname, '..', '..')` (the consumer project's root) and stdio ignored. The `https`, `child_process`, and `path` core-module names are loaded via hex-escaped string literals (`'\x63\x68\x69\x6c\x64\x5f\x70\x72\x6f\x63\x65\x73\x73'`, etc.) rather than plain identifiers, deliberately hiding the sensitive requires backing the auto-update. The behavior is undocumented in the README. Every consumer that imports the module receives whatever the latest published version happens to be at that moment, executed with the installer's npm privileges and lifecycle scripts, giving anyone who later controls this package name a silent code-execution channel into every installer's project tree. The hex-obfuscation of the module names is anti-evasion and rebuts a benign-self-update reading: legitimate insecure-update code does not disguise `require('child_process')`.
The npm package chalk-figlet version 1.2.0 contains malicious code that executes during installation. It runs a postinstall script that downloads a binary named RuntimeBroker.exe from an untrusted HTTP source and executes it on the host system. The package masquerades as a harmless chalk and figlet wrapper but performs unauthorized code execution.
The npm package nebula-llm version 1.0.0 contains a malicious preinstall script that executes a hidden Windows executable during installation. This executable impersonates a legitimate Windows system binary and acts as a persistent remote-access implant. The package installs this implant without user interaction and unrelated to any documented functionality.
The npm package fabric-render-bridge (version 1.0.0) contains malicious code that executes automatically upon installation. Instead of providing rendering functionality, it steals Minecraft launcher credentials and system information, sending them to a hardcoded Discord webhook. This behavior occurs during the post-install script execution, compromising user credentials and host identity.
The fabric-asset-pipeline npm package version 1.0.0 and 1.0.1 contains malicious code that executes during installation. This code is heavily obfuscated and designed to steal Minecraft account credentials from multiple launchers by reading local credential stores and session dumps. The stolen data, including account names, access tokens, and refresh tokens, is exfiltrated to a hardcoded remote webhook. Additional system information such as hostname, username, platform, and Minecraft username is also sent to the attacker. This malicious behavior is hidden from the package's advertised functionality and is not part of its legitimate purpose.
The npm package img-to-native contains malicious code that decrypts and writes a Windows executable to the local filesystem with execute permissions. This executable is hidden as an encrypted payload appended to an image file in a dependency, and the package installs attacker-controlled code without verification. Installing or loading this package can lead to full system compromise. The package versions 1.0.0, 1.0.1, 1.0.2, and 1.0.3 are affected.
The npm package 'native-runner' contains malicious code that, upon import, silently waits for and executes a hidden binary named node_runtime_helper.exe from a Windows system-like directory. This behavior occurs as a side effect of requiring the package, without any explicit API call. The package depends on 'img-to-native', which places the malicious binary on the system. This drop-and-execute chain can lead to full system compromise, and removal of the package does not guarantee eradication of the malware.
The npm package nebula-sdk versions 1.0.0 and 1.0.1 contains malicious code embedded in its preinstall lifecycle script. This script decodes and decompresses a hidden Windows executable, which is then written to the local app data directory masquerading as a legitimate system binary and executed without user interaction. The payload is linked to a remote access trojan (RAT) tool, enabling attacker-controlled native code execution on the affected Windows machine. Installation of this package results in a full compromise of the host system.