Which versions of golan125-homepage-test are malicious?

The following npm versions of golan125-homepage-test are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate golan125-homepage-test if I installed it?

Remove golan125-homepage-test from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed golan125-homepage-test — how do I know if it already compromised me?

If golan125-homepage-test 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 golan125-homepage-test part of a known attack campaign?

Yes — golan125-homepage-test is associated with the RLMA-2026-05549, IN-MAL-2026-013152, RLUA-2026-06262 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 golan125-homepage-test 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 golan125-homepage-test (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging golan125-homepage-test across your stack and pipelines.

Malicious package

golan125-homepage-testnpm

golan125-homepage-test is a confirmed malicious npm package (MAL-2026-10897) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in golan125-homepage-test (npm)

MAL-2026-10897

Immediate action

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

npm uninstall golan125-homepage-test

What this malware does

Package self-identifies as a security research test ('Security research test - do not install'). The package.json homepage field contains javascript:alert(document.domain), which is an XSS probe targeting any registry or UI frontend that renders homepage values as clickable links without sanitization. The package has no lifecycle scripts (no preinstall/install/postinstall), no network I/O, and index.js exports an empty object — installing or requiring this package does not harm the installer's machine. The XSS probe targets registry web UI rendering, not developers who install the package.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

9de97a7b84132655982784c44670e7d7362fe9b1e7fbb1bd98b156b55014ff6c

705b0dc2e3b9aafb6d0e72ecb5ad51d873cd59104a045f74bb27161c87a24960

42bfb74872fd09d5186219f7dae76465ad6a926d608b7da6702960271630ec94

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for golan125-homepage-test (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging golan125-homepage-test across your stack and pipelines.
If you installed it — respond
Remove golan125-homepage-test from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If golan125-homepage-test 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 golan125-homepage-test 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. golan125-homepage-test 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

RLMA-2026-05549IN-MAL-2026-013152RLUA-2026-06262

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks golan125-homepage-test-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database