Which versions of jslint-config are malicious?

The following npm versions of jslint-config are flagged malicious: 10.22.2. Treat any of these as compromised.

How do I remediate jslint-config if I installed it?

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

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

Yes — jslint-config is associated with the GHSA-39pg-5x8j-wg53 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 jslint-config 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 jslint-config (version 10.22.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jslint-config across your stack and pipelines.

Malicious package

jslint-confignpm

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

MAL-2026-1055

Immediate action

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

npm uninstall jslint-config

What this malware does

The package jslint-config 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.

The OpenSSF Package Analysis project identified 'jslint-config' @ 10.22.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

10.22.2

Indicators of compromise (SHA-256)

b759b345e0ed809730a90556110527d6f94c14b68d118872334ccb7949fd874b

11f2fdea43a54f2aac247e06fcc46c506979a5b1ccb5d178077662e61f747b74

bddd0b74c730da3b118b7ef92befbc93b4b1379cc23ce7535e843151a84ae957

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

Campaign

GHSA-39pg-5x8j-wg53

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks jslint-config-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