# MAL-2026-10505: Malicious code in express-ini (npm)


- **Type:** Malicious package
- **Package:** `express-ini` (npm)
- **Published:** 13 Jul 2026
- **Also known as:** GHSA-w3p6-c3cm-r253

## What is MAL-2026-10505?

MAL-2026-10505 is a malicious package in express-ini, published on 13 Jul 2026. 

### Official description

package.json declares postinstall=`node index.js`. index.js is heavily obfuscated (obfuscator.io rotated string-array with RC4-based decoders hiding all identifiers and literals). At install time the script imports fs, os, path, crypto, child_process and a network module, installs silent uncaughtException/unhandledRejection handlers to suppress errors, performs a remote lookup, splits the response on ':', base64-decodes it, AES-decrypts it via crypto.createDecipheriv, writes the decrypted bytes to a file under process.cwd(), and executes it via child_process.execSync with windowsHide:true. The package name suggests an Express.js utility and the README describes an unrelated 'Safe Wrapper Module', but the only shipped code is the dropper — the name and README are cover for install-time remote code execution against the installer's machine.

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.

## What should I do about MAL-2026-10505?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-10505 is a malicious package: express-ini (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-10505/ (Markdown: https://insights.sbomify.com/MAL-2026-10505/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-10505

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-10505/
Summaries are generated and may contain mistakes; the official description above is the record.