Which versions of 100jsss are malicious?

The following npm versions of 100jsss are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate 100jsss if I installed it?

100jsss is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed 100jsss — how do I know if it already compromised me?

If 100jsss was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is 100jsss part of a known attack campaign?

Yes — 100jsss is associated with the IN-MAL-2026-002325 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 100jsss across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for 100jsss (version 1.0.0).

Malicious package

100jsssnpm

Advisory published May 12, 2026Updated May 13, 2026

100jsss is a confirmed malicious npm package (MAL-2026-3669) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in 100jsss (npm)

MAL-2026-3669

Immediate action

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

npm uninstall 100jsss

What this malware does

The main entry g.js constructs an image beacon whose src is a base64-decoded attacker URL (https://w.g32.com/g?k=) concatenated with btoa(document.location.href + '*' + document.cookie), exfiltrating the current URL and cookies cross-origin. The destination host is deliberately hidden behind atob() to evade string-based scanning. The package has placeholder metadata, no real functionality, and a trivial README, consistent with a malicious PoC/throwaway upload rather than a legitimate library. Obfuscation + exfiltration + credential-theft target (document.cookie) is an unambiguous malicious combination.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

207a07d918d9b3ddfdf0f845ec22f6bab19629fa77968d3b41409d0b62bad441

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for 100jsss (version 1.0.0).
If you installed it — respond
100jsss is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If 100jsss was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. 100jsss on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002325

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks 100jsss-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database