Which versions of @osmanekrem/error-handler are malicious?

The following npm versions of @osmanekrem/error-handler are flagged malicious: 1.2.2. Treat any of these as compromised.

How do I remediate @osmanekrem/error-handler if I installed it?

@osmanekrem/error-handler 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.

I already installed @osmanekrem/error-handler — how do I know if it already compromised me?

If @osmanekrem/error-handler 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.

Is @osmanekrem/error-handler part of a known attack campaign?

Yes — @osmanekrem/error-handler is associated with the GHSA-xcwf-q72p-w435 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @osmanekrem/error-handler across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @osmanekrem/error-handler (version 1.2.2).

Malicious package

@osmanekrem/error-handlernpm

Advisory published Nov 24, 2025Updated Dec 1, 2025

@osmanekrem/error-handler is a confirmed malicious npm package (MAL-2025-191047) that steals credentials and exfiltrates sensitive data (malicious version 1.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @osmanekrem/error-handler (npm)

MAL-2025-191047

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @osmanekrem/error-handler

What this malware does

The package @osmanekrem/error-handler was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.2.2

Indicators of compromise (SHA-256)

c659c1b21b005088bc9ccdcef5931d8d358388e26cbc633e67ebb7d6906b0520

b55741ef21e19173784c5b2d2321e780f7759269f9286a472ffec419d4bf19f9

cdab7fccd69174b679d09ccf0c5654e5c508d2456a494080d5f2794de083e770

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @osmanekrem/error-handler (version 1.2.2).
If you installed it — respond
@osmanekrem/error-handler 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 @osmanekrem/error-handler 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

No. @osmanekrem/error-handler on npm has been identified as a malicious package (version 1.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xcwf-q72p-w435

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @osmanekrem/error-handler-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database