Which versions of luxon-js are malicious?

Every published version of luxon-js on npm is considered malicious. Remove the package entirely.

How do I remediate luxon-js if I installed it?

Remove luxon-js 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 luxon-js — how do I know if it already compromised me?

If luxon-js 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 luxon-js part of a known attack campaign?

Yes — luxon-js is associated with the GHSA-phgx-7qqx-fxcj 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 luxon-js 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 luxon-js (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging luxon-js across your stack and pipelines.

Malicious package

luxon-jsnpm

Malicious code in luxon-js (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-228

Immediate action

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

npm uninstall luxon-js

What this malware does

The package luxon-js 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

4fc26738db6a8729f71b32abddd5b6da3cce0b05e304b180ed3915f6cd07f746

f6cf8bc36e6ae424cba2eb02275c950a8211e5342252662276b2c53afa5c8255

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

Campaign

GHSA-phgx-7qqx-fxcj

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks luxon-js-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