audit-logsssnpm
Advisory published Updated
audit-logsss is a confirmed malicious npm package (MAL-2026-4487) that steals credentials and exfiltrates sensitive data (malicious version 8.0.9). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in audit-logsss (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for audit-logsss (version 8.0.9).
If you installed it — respond
audit-logsss is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If audit-logsss was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks audit-logsss-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.