How severe is GHSA-fgfj-rj24-mj7q?

No CVSS score has been assigned to GHSA-fgfj-rj24-mj7q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fgfj-rj24-mj7q?

GHSA-fgfj-rj24-mj7q affects the following packages: kraken-api (npm). Ecosystems affected: npm.

How do I fix GHSA-fgfj-rj24-mj7q?

No patched version of kraken-api has shipped for GHSA-fgfj-rj24-mj7q yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-fgfj-rj24-mj7q in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kraken-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-fgfj-rj24-mj7q if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-fgfj-rj24-mj7q actively exploited in the wild?

No public exploit code has been indexed for GHSA-fgfj-rj24-mj7q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-fgfj-rj24-mj7q published, and has it been updated?

GHSA-fgfj-rj24-mj7q was published on September 2, 2020 and was last updated on July 27, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

Malicious Package in kraken-apiGHSA-fgfj-rj24-mj7q

GHSA-fgfj-rj24-mj7q is a security vulnerability in kraken-api. No vendor fix is recorded yet; mitigation options are listed below.

Published

Sep 2, 2020

Updated

Jul 27, 2023

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Jul 27, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

kraken-apinpm

3Kdownloads / week

Description

Version 0.1.8 of kraken-api contains malicious code as a postinstall script. When installed, the package calls home to a Command and Control server to execute arbitrary commands.

Recommendation

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.

Users may consider downgrading to version 0.1.7 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.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
📦npm	`kraken-api`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kraken-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of kraken-api has shipped for GHSA-fgfj-rj24-mj7q yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Version 0.1.8 of `kraken-api` contains malicious code as a postinstall script. When installed, the package calls home to a Command and Control server to execute arbitrary commands. ## Recommendation 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. Users may consider downgrading to version 0.1.7 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 p

O3 Security · Impact-Aware SCA

Is GHSA-fgfj-rj24-mj7q in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works