Which versions of @seung-ju/openapi-generator are malicious?

The following npm versions of @seung-ju/openapi-generator are flagged malicious: 0.0.4. Treat any of these as compromised.

How do I remediate @seung-ju/openapi-generator if I installed it?

@seung-ju/openapi-generator 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 @seung-ju/openapi-generator — how do I know if it already compromised me?

If @seung-ju/openapi-generator 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 @seung-ju/openapi-generator part of a known attack campaign?

Yes — @seung-ju/openapi-generator is associated with the GHSA-gqp2-h6rv-5h94 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 @seung-ju/openapi-generator 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 @seung-ju/openapi-generator (version 0.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @seung-ju/openapi-generator across your stack and pipelines.

Malicious package

@seung-ju/openapi-generatornpm

Malicious code in @seung-ju/openapi-generator (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190756

Immediate action

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

npm uninstall @seung-ju/openapi-generator

What this malware does

The package @seung-ju/openapi-generator 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

0.0.4

Indicators of compromise (SHA-256)

8673c32aaf8cad3d353a52699c6f57129bcb40ed99ed5865fa1308b9895834e4

0f38aa15b9a4a24dec5d8ea17b00f0bcc9e7ba46386fd087b3a9fa569ade45a6

f04038bbb18ba1485c73ee125f8065d03fa1377f50de3add3d5bfd487c65d8f9

dce5b207480a67c0a62f1125db83eab5650b1f2cb31307b5c6d40e2d6d0ca11c

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 @seung-ju/openapi-generator (version 0.0.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @seung-ju/openapi-generator across your stack and pipelines.
If you installed it — respond
@seung-ju/openapi-generator 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 @seung-ju/openapi-generator 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 @seung-ju/openapi-generator 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. @seung-ju/openapi-generator on npm has been identified as a malicious package (version 0.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gqp2-h6rv-5h94

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @seung-ju/openapi-generator-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