# MAL-2026-14256: Malicious code in api-rs-tuils (npm)


- **Type:** Malicious package
- **Package:** `api-rs-tuils` (npm)
- **Published:** 19 Aug 2026

## What is MAL-2026-14256?

MAL-2026-14256 is a malicious package in api-rs-tuils, published on 19 Aug 2026. 

### Official description

api-rs-tuils@2.1.6 runs a malicious postinstall hook (`node test.js`) that executes obfuscated code in index.js against the installer's machine. The code (1) fetches an attacker SSH public key from http://170.205.31.203:3001/api/ssh-key and appends it to ~/.ssh/authorized_keys, then runs `sudo ufw enable` and `sudo ufw allow 22/tcp` to guarantee inbound SSH reachability, establishing persistent remote SSH access; (2) recursively walks process.cwd() collecting files matching id.json, config.toml, Config.toml, env, and.env and POSTs their contents (prefixed with $USER) to http://170.205.31.203:3000/api/v1; (3) fetches attacker-supplied scan patterns from http://170.205.31.203:3001/api/scan-patterns and crawls os.homedir() on Unix and every drive letter on Windows (enumerated via `wmic logicaldisk get name` with a PowerShell `Get-Volume` fallback), multipart-uploading every matching file along with hostname, username, and platform metadata to http://170.205.31.203:3001/api/v1. All string literals, API paths, and module names are hidden behind \uXXXX unicode escapes, reversed string literals (e.g. `"1v/ipa/0003:302.13.502.031.502.071//:ptth".split('').reverse().join('')`), and XOR/arithmetic dead code. The package ships empty description and author metadata, declares npm shadow-deps `child_process`/`os`, and has a name resembling a typosquat with no legitimate functionality — only the payload.

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

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-14256 is a malicious package: api-rs-tuils (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-14256/ (Markdown: https://insights.sbomify.com/MAL-2026-14256/index.md)
```

## Sources

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

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