Which versions of @asyncapi/protobuf-schema-parser are malicious?

The following npm versions of @asyncapi/protobuf-schema-parser are flagged malicious: 3.5.2, 3.5.3, 3.6.1. Treat any of these as compromised.

How do I remediate @asyncapi/protobuf-schema-parser if I installed it?

@asyncapi/protobuf-schema-parser 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 @asyncapi/protobuf-schema-parser — how do I know if it already compromised me?

If @asyncapi/protobuf-schema-parser was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @asyncapi/protobuf-schema-parser part of a known attack campaign?

Yes — @asyncapi/protobuf-schema-parser is associated with the GHSA-2wj6-h4j4-v3mm 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 @asyncapi/protobuf-schema-parser across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @asyncapi/protobuf-schema-parser (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @asyncapi/protobuf-schema-parser across your stack and pipelines.

Malicious package

@asyncapi/protobuf-schema-parsernpm

Malicious code in @asyncapi/protobuf-schema-parser (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190641

Immediate action

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

npm uninstall @asyncapi/protobuf-schema-parser

What this malware does

The package @asyncapi/protobuf-schema-parser 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

3 flagged

3.5.23.5.33.6.1

Indicators of compromise (SHA-256)

168e82e52e9cb5981c55fecfe6de33adbed4275cc00a846a172e924d332e8495

927e5dcfc89c461512068769c97bb06898751cd42cd15f50d97c4760c658269b

52772a07703b85b9524ac28502f9d5cff1a02fdf2607676d8512873036687391

81ca66e7654ce7fc0f7a75138233275eaf6c302a0f9a923007c52e829dcd0797

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @asyncapi/protobuf-schema-parser (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @asyncapi/protobuf-schema-parser across your stack and pipelines.
If you installed it — respond
@asyncapi/protobuf-schema-parser 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 @asyncapi/protobuf-schema-parser was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @asyncapi/protobuf-schema-parser before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. @asyncapi/protobuf-schema-parser on npm has been identified as a malicious package (versions 3.5.2, 3.5.3, 3.6.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2wj6-h4j4-v3mm

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @asyncapi/protobuf-schema-parser-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