Which versions of @0xlr/test-callback are malicious?

The following npm versions of @0xlr/test-callback are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @0xlr/test-callback if I installed it?

@0xlr/test-callback 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 @0xlr/test-callback — how do I know if it already compromised me?

If @0xlr/test-callback 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 @0xlr/test-callback part of a known attack campaign?

Yes — @0xlr/test-callback is associated with the GHSA-p6vh-r7p3-72r9, IN-MAL-2026-013188 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 @0xlr/test-callback across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @0xlr/test-callback (version 1.0.0).

Part of a larger attack: @0xlr published 10 malicious packages. See the full campaign →

Malicious package

@0xlr/test-callbacknpm

Advisory published Jul 31, 2026Updated Aug 5, 2026

@0xlr/test-callback is a confirmed malicious npm package (MAL-2026-11433) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @0xlr/test-callback (npm)

MAL-2026-11433

Immediate action

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

npm uninstall @0xlr/test-callback

What this malware does

@0xlr/[email protected] is a minimal package with no observed installer-harm behavior. No lifecycle scripts performing network fetches or shell execution, no credential or environment scraping, no hardcoded exfiltration endpoints, and no obfuscated payloads were observed in the scanned files.

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

0fef68e7a34cfe91649a86535f07fa0373d6231d06a296f9b7f3b3a4c47ed6e5

09f54fc6282ea45cdd155c621f41ce7bb3d8f5622ba8eef14cec7e97397b3efa

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @0xlr/test-callback (version 1.0.0).
If you installed it — respond
@0xlr/test-callback 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 @0xlr/test-callback 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. @0xlr/test-callback on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-p6vh-r7p3-72r9IN-MAL-2026-013188

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @0xlr/test-callback-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