# MAL-2026-4487: Malicious code in audit-logsss (npm)


- **Type:** Malicious package
- **Package:** `audit-logsss` (npm)
- **Published:** 22 May 2026
- **Also known as:** GHSA-gcq4-52q3-v4fm

## What is MAL-2026-4487?

MAL-2026-4487 is a malicious package in audit-logsss, published on 22 May 2026. 

### Official description

The package's postinstall script executes shell reconnaissance (`id || ver && whoami && hostname`), fetches the installer's public IP from api.ipify.org, collects USERDOMAIN/COMPANY environment variables, hostname, and cwd, then POSTs the aggregated JSON to an attacker-controlled Project Discovery Interactsh subdomain at `yihpvsviuggxabauqtuedjfyzjlrtkpzx.oast.fun`. The exfiltrated payload self-identifies as `package_name:'audit-logs'` while the published name is `audit-logsss` (triple-s), confirming the package is a deliberate typosquat of the legitimate `audit-logs` package designed to profile any developer who fat-fingers the install command. The beacon fires automatically on `npm install` without user consent.

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

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

## Sources

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

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