Malicious Code Injection in okta-getas53-breki Package - npm Vulnerability
Summary
MAL-2025-74781: Malicious code in okta-getas53-breki (npm). Affected versions are not published. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The okta-getas53-breki package is part of the npm ecosystem, primarily used for JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts that manipulate package metadata and publish numerous derivative versions to inflate developer reputation scores.
Vulnerability Detail
The vulnerability in the okta-getas53-breki package stems from its inclusion in a malicious campaign that modifies the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include potential pollution of the npm registry, unauthorized access to sensitive information, and compromise of developer reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall okta-getas53-brekiIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As an immediate workaround, consider removing the okta-getas53-breki package from your project if it is not essential. You can do this by executing the command: npm uninstall okta-getas53-breki. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The okta-getas53-breki package has been identified as part of a malicious campaign that poses significant risks to developers and their applications. It is crucial to take immediate action by updating or removing the package to safeguard your projects from potential threats.
See every vulnerability recorded for okta-getas53-breki →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, which has been linked to malicious activities.
The vulnerability can lead to unauthorized modifications of your package metadata and potential security risks due to the pollution of the npm registry.
You should update the package to the latest version or remove it from your project to mitigate the risk.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without signing up.
