Ghost, a Node.js content management system, has a server-side request forgery (SSRF) vulnerability affecting versions from 6.26.0 up to but not including 6.54.1. This flaw allowed unauthenticated users to abuse certain functionality, such as Webmentions, to make limited HTTP requests to internal hosts on the Ghost server's network. The vulnerability does not expose response data to the attacker. The issue is fixed in version 6.54.1.
The npm package cardsmobile-cardsmobile-core version 35.6.6 contains malicious code that, when required, loads a platform-specific payload from attacker-controlled Cloudflare Workers hosts. This payload is an unsigned executable fetched and saved to hidden temporary directories with decoy names, then executed with detached persistence. The package uses obfuscation techniques to evade static analysis and enables remote code execution on the host machine beyond the Node.js process lifetime.
The npm package 'checkout-confirm-pos-order-sms-am' version 35.6.4 contains malicious code that executes attacker-controlled native binaries on the installer's machine. Upon requiring the package, it downloads an opaque binary from obfuscated Cloudflare Workers endpoints or via DNS-TXT fallback from specific domains, writes it to a temporary directory under disguised filenames, sets executable permissions, and spawns it detached from the Node.js process. The package uses string splitting and base64 chunk assembly to evade static detection. This behavior effectively results in remote code execution on the host system.
The npm package 'chai-as-inspired' is a typosquatting malicious package that executes attacker-controlled JavaScript code with full Node.js privileges. It achieves this by spawning a detached child process that fetches remote code from a mutable JSON storage endpoint, then executes it in a retry loop. The remote code can be changed at any time by the attacker, enabling ongoing malicious activity. This package version 2.2.4 is affected.
The npm package 'editor_application' version 9999.0.0 contains malicious code that executes a preinstall hook running 'node callback.js'. This code collects host identifiers and private CI repository information from environment variables and sends them via an unencrypted HTTP GET request to an attacker-controlled IP address. This behavior is indicative of a dependency confusion attack beacon designed to map internal package namespaces and CI environments of affected organizations.
The npm package 'tick-forge' version 11.5.2 contains malicious code that fetches and executes attacker-controlled JavaScript from a hardcoded IP address. This code execution occurs within the Node.js runtime with full privileges, potentially compromising any system using this package. The malicious loader disguises its network activity with icon and CDN-like naming but communicates over plain HTTP to a bare IP address. Systems with this package installed should be considered fully compromised, and all secrets and keys on those systems must be rotated. Removal of the package alone may not eliminate the compromise.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (49d47be3f5dc16ea70755e0233f46106d3f50d1d5384a4f20c76b91463c9876c)
The package's main entry defines a getPlugin() function that performs an HTTPS request to a hardcoded bare-IP endpoint at 31.97.137.157:45000/icons/112 and passes the response field data.credits to `new Function('require','module',...,'Promise', data.credits)`, executing whatever the remote host returns with full Node.js context including require, process, Buffer, and globalThis. The destination URL is assembled from split protocol/separator/domain/path fragments and wrapped in benign 'icon/CDN' naming that hides the code-execution sink. The declared dependencies (@primno/dpapi for Windows DPAPI unwrap of browser-stored secrets, node-machine-id for host fingerprinting, better-sqlite3/sqlite3 for browser profile databases, socket.io-client) do not correspond to the advertised 'crypto checkout' purpose and pre-stage tooling a remote payload can invoke via the injected require() to harvest Windows browser credentials and cookies. Any consumer that require/imports this package and reaches the getPlugin path grants the remote operator arbitrary code execution on the installer's machine.
## Source: ghsa-malware (cad454e0e312c87020333f7ece00363eb627c8b1b1334431c662c09a6af7dad1)
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 dust-helpers version 9999.0.0 contains malicious code that executes during installation. Its preinstall script runs a Node.js script that collects sensitive environment information including hostname, username, current working directory, internal registry URL, and CI repository identifiers. This data is exfiltrated via an HTTP GET request to an attacker-controlled IP address. The package is a dependency confusion attempt, published with a very high version number to trick private builds into installing it and revealing internal details to attackers.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (b15806df14aa955b2d5e08414d4f22ad71a9d1ac823aa7557e8f9d490d78761d)
index.js exports getPlugin() which issues an HTTPS request to a hardcoded bare-IP endpoint at https://46.183.25.232:45000/icons/112 and passes the response field data.credits to new Function('require','module',...,data.credits), executing attacker-controlled JavaScript with require, process, and Buffer injected. The request is framed with cover-story naming (a font-awesome/CDN path fragment and a 'bearrtoken: logo' header) that is unrelated to the actual bare-IP destination and inconsistent with the package's stated 'crypto checkout' purpose. Declared dependencies (@primno/dpapi for Windows DPAPI unwrap, node-machine-id, better-sqlite3) are consistent with a credential/wallet-stealer payload delivered through the loader.
## Source: ghsa-malware (36320c265cebe6479c4c4d438a043d4c38fb14b9e02bd8f97130c557b19a2b2c)
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.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (6921f72a1b4fbaaba87fcbe3cb30137815e7e2bb932ffa794acd0010b8954c5f)
package.json declares `preinstall: node index.js`, causing index.js to run automatically on `npm install`. The script collects installer-side data — hostname, username, home directory, DNS server list, current working directory, package.json contents, and the contents of /etc/passwd and /etc/hosts — and HTTPS-POSTs it to a hardcoded Burp Collaborator subdomain at 5z5h9l8e7cktx1ihl6usn4zgb7h15rtg.oastify.com. The exfiltration fires unconditionally on install with no user interaction.
## Source: ghsa-malware (fb3a6a289e12028cd0778c9ca9e56392a64003291be3756d28490d76c491e249)
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 async-mutex-v3 version 3.1.0 is a malicious typosquat that executes attacker-controlled JavaScript code with Node.js privileges. Its default export makes an HTTP request to a hardcoded IP address and runs the returned code, enabling remote code execution. The package masquerades as an icon CDN helper but actually includes dependencies consistent with credential-stealing post-exploitation tools. Any user importing and invoking the default export will execute arbitrary code from the attacker-controlled server.
The poly-bbc-service npm package version 3.7.2 contains malicious code that fetches and executes remote code with full Node.js privileges. The package's getPlugin function makes an HTTPS request to a hardcoded IP address and executes the response's data.credits field as a function, granting extensive system access. The package also includes unused code suggesting a cover story inconsistent with its advertised purpose. Dependencies indicate potential staging for extracting browser credentials or Windows DPAPI-protected secrets.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (e195fef439eb6af3d28576857a30030e4bd839406fa36b2f939279743f12188e)
The package is advertised as a mutex-lock utility but ships none of the documented API (no Mutex/lock/unlock). Its sole export, getPlugin in index.js, assembles a URL from split protocol/domain/path variables resolving to https://31.97.137.157:45000/icons/108, fetches a JSON response, and passes the response field data.credits to new Function(...) invoked with full require/process/Buffer context — executing attacker-controlled JavaScript on the caller's host. Variable framing references CDN names (cloudflare, fastly, akamai, cdnjs/font-awesome) as a decoy over a bare-IP destination unrelated to any CDN. Declared dependencies (@primno/dpapi, node-machine-id, better-sqlite3, socket.io-client) are consistent with infostealer staging (DPAPI decryption, machine fingerprinting, SQLite reads of browser stores, socket-based C2). The name resembles the popular async-mutex package.
## Source: ghsa-malware (1f07bc4e9d844bdfd01a18eb7fb1efecbba0e9a1380f2b23bddf708fa4c24c52)
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.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (5e0e5eedb2c2a44513fd808788f02499f57e3c2877c4c69d8a84b0d4038d7fe0)
@cy4dev/cydemo-bg-color@7.0.0 ships a postinstall lifecycle script (src/postinstall.js) that runs at `npm install` time and invokes node:child_process.exec with two shell commands. The first, `curl -X POST -d \`env | grep AWS\` http://localhost:8000`, enumerates AWS_*-prefixed environment variables from the installer's shell and POSTs them as the request body — a functioning credential-exfiltration primitive against the installer's environment. The second, `open /System/Applications/Calculator.app`, launches a GUI application on macOS, demonstrating arbitrary host-shell execution triggered solely by installing the package. The package advertises itself as a DOM background-color helper; the postinstall behavior has no build or runtime purpose consistent with that description. The exfiltration destination in this build is loopback (localhost:8000), so the AWS credentials do not leave the host in this specific version, but the credential-scrape and arbitrary-exec code paths execute unconditionally on every install.
The npm package 'alpha-helper' version 1.3.4 contains malicious code that executes attacker-controlled JavaScript with full Node.js privileges. The exported function makes an HTTPS request to a hardcoded IP address and uses the response to dynamically construct and run code via the Function constructor. The package disguises itself with unrelated documentation and dependencies consistent with credential extraction. This behavior allows arbitrary code execution in any environment that imports and runs this package.
The @nextco/utils npm package version 5.0.0 contains malicious code that executes upon module load. It collects host reconnaissance data including hostname, username, directory paths, OS/architecture, Node.js version, and environment variable names. This data is base64-encoded and sent via an unencrypted HTTP POST request to a hardcoded attacker-controlled server (attacker.cl). The package does not provide an opt-out for this telemetry, exposing sensitive host information to attackers.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (6c8ce91cbe1aaa587613795b1b82cc84384b499a29af4a18c0a820b77ea1d834)
The npm package ach-detail@99.0.1 ships a preinstall lifecycle script (scripts/preinstall.js) that runs automatically on `npm install`. The script collects the installer's hostname, package name and version, Node.js version, platform, timestamp, and a nonce, and POSTs the payload to a hardcoded remote endpoint at https://callback.kuldeep.io/beacon, with an HTTP fallback to the same host. The package is published to the public npm registry at version 99.0.1 — a version-inflation pattern consistent with dependency-confusion targeting of a private internal package of the same name. A log string in the script self-labels the behavior as an authorized bug-bounty PoC, but that label is author-controlled, does not change the observable behavior, and does not represent consent from any installer that resolves the package (accidentally or through dependency-confusion). Installer-side host identifiers leave the machine to a non-first-party endpoint on install.
The npm package rollup-plugins-check versions 0.0.1 and 0.0.2 contains malicious code that executes arbitrary JavaScript fetched from a remote server during installation. This code disables TLS certificate verification, allowing attackers to intercept and modify the payload. The package masquerades as a legitimate rollup polyfill plugin but includes a postinstall script that runs potentially harmful code with full access to Node.js require functionality.
The npm package 'npm-module-service' version 3.7.2 contains malicious code that performs an HTTPS request to a hardcoded IP address and executes attacker-supplied JavaScript code with full Node.js privileges on the host. The module masquerades as a CDN icon helper but actually targets an unauthenticated bare-IP host, enabling remote code execution when the module is imported and used.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (6b9fb0d73b7d26454a227e93754f11ff2405424b1279490863055e8d8c8c6498)
Package targets the electrode-io internal name `electrode-ota-ui-app` with an inflated 99.0.1 version to win dependency resolution against a private registry. package.json declares both `main: index.js` and `scripts.postinstall: node index.js`, so on `npm install` and on any `require()` the package unconditionally runs `collectAndSend()` in index.js. That function gathers host identifiers via `os.hostname()`, `os.userInfo()`, `os.platform()`, and `os.release()`, resolves the installer's public IP via ipify and geo/ISP data via ipapi.co, and POSTs a JSON payload to the hardcoded Burp Collaborator subdomain `https://itfv50wbocctx0j32fyfq8z7uy0ptdn1c.oastify.com/callback`, controlled by the package author. README self-labels as a dependency-confusion PoC, but the callback is live and any installer whose resolver picks this public package over the intended internal one is compromised.