nolby
This report shows the evidence for nolby@1.0.3. 4 of 5 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10980 confirms this npm version as malicious.
Advisory
MAL-2026-10980
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in nolby (npm)
Details
The package advertises itself as a pure calendar/streak math library with no import-time side effects, but index.mjs invokes a top-level `_sync()` on module load. When loaded on a Linux process with access to `/mnt/c` (a WSL environment), the function enumerates Windows user profiles under `/mnt/c/Users` and writes the bundled `cache.dat` bytes to `AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\vite-native-helper.exe` under the first user's profile. The shipped `cache.dat` is a Windows PE executable (contains the `!This program cannot be run in DOS mode` stub and standard PE sections `.rdata`, `.pdata`, `.reloc`); it is declared in the `files` array as opaque data and renamed at write time to a Vite-lookalike filename. Placement in the Startup folder causes the PE to execute on the Windows user's next login, establishing persistent code execution on the WSL host's Windows side triggered by a normal `require`/`import` of the package.
## Source: ghsa-malware (b21eb09af067749fee65992ad1d26cfca82a29b74c3298b9c7a87fa7052e179f) 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.
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to nolby@1.0.3.
The same advisory and Firewall decision cover 4 recorded versions
1.0.2, 1.0.3, 1.0.0, 1.0.1
The versions list below shows the verdict for each recorded version.
- Avoid installing nolby@1.0.3. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.