MalwarePublished 22 Jul 2024Updated 30 Oct 2025

chromestatus-openapi (npm) · Malicious Code

Affects chromestatus-openapiSource GCVE Database

Malicious package : remove chromestatus-openapi and rotate any secrets on hosts that installed it.

Data as of 29 Oct 2026, 22:55 UTC

Classification

Malicious package

Published to npm · OSV MAL-2024-7783

What to do

Remove chromestatus-openapi from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npmchromestatus-openapi	Affected =69.69.69 =71.69.69 =1.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The 'chromestatus-openapi' npm package versions 69.69.69, 71.69.69, and 1.0.0 are identified as malicious. During installation, it runs an info stealer that targets npm, git, and CI/CD tokens by communicating with a domain linked to malicious activity. Systems with this package installed should be considered fully compromised, and all secrets and keys stored on those systems must be rotated immediately from a separate, secure device.

Impact

Any system with this package installed is considered fully compromised. Attackers may have obtained npm, git, and CI/CD tokens, potentially allowing unauthorized access to source code repositories, deployment pipelines, and other sensitive infrastructure. This can lead to further compromise, data leakage, and unauthorized code execution within affected environments.

Defensive guidance

Immediately remove the 'chromestatus-openapi' package from all affected systems. Rotate all secrets, tokens, and keys that were stored or used on the compromised systems, ensuring this is done from a separate, secure device. Because full system compromise is possible, consider performing a thorough forensic analysis and system rebuild to ensure complete remediation.

Summary

The 'chromestatus-openapi' package on npm, specifically versions 69.69.69, 71.69.69, and 1.0.0, has been flagged as malicious by multiple sources including the OpenSSF Package Analysis project and Google Open Source Security. The package installs a dependency from a custom domain that executes an information-stealing payload during installation. This payload focuses on exfiltrating sensitive tokens related to npm, git, and CI/CD environments. The package communicates with domains associated with malicious activity, indicating active data theft. Due to the nature of the compromise, removal of the package alone does not guarantee system remediation.

References

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2026, 22:55 UTC

Technical details

References

Community reviews