Which versions of @asyncapi/java-spring-template are malicious?

The following npm versions of @asyncapi/java-spring-template are flagged malicious: 1.6.1, 1.6.2. Treat any of these as compromised.

How do I remediate @asyncapi/java-spring-template if I installed it?

@asyncapi/java-spring-template 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/java-spring-template — how do I know if it already compromised me?

If @asyncapi/java-spring-template 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/java-spring-template part of a known attack campaign?

Yes — @asyncapi/java-spring-template is associated with the GHSA-6w4j-664j-g45g 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/java-spring-template 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/java-spring-template (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @asyncapi/java-spring-template across your stack and pipelines.

Malicious package

@asyncapi/java-spring-templatenpm

Malicious code in @asyncapi/java-spring-template (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190716

Immediate action

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

npm uninstall @asyncapi/java-spring-template

What this malware does

The package @asyncapi/java-spring-template 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

2 flagged

1.6.11.6.2

Indicators of compromise (SHA-256)

a8191bff82322933f626c94461a64d592755eb5e5df4e4262c76d4a3644667cb

5bb0637829fe4777b541f94a01279132c65a2d361e3d762ce0a08dd813e7fd5f

0e86f865b25e5658d47ae23ed2a22f2dd9f2b8375dcf6226e29f8d856b8c6df3

57c479ff5a2ca54bb0571ec8dc24e92baac1afd85cb454c6295b8a08ae71ee89

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

Campaign

GHSA-6w4j-664j-g45g

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @asyncapi/java-spring-template-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