# MAL-2026-10700: Malicious code in time-format-kit (npm)


- **Type:** Malicious package
- **Package:** `time-format-kit` (npm)
- **Published:** 16 Jul 2026

## What is MAL-2026-10700?

MAL-2026-10700 is a malicious package in time-format-kit, published on 16 Jul 2026. 

### Official description

On npm install, the package's postinstall script decodes base64-encoded shell payloads and executes them via an obfuscated child_process.exec lookup (require('ch'+'il'+'d_p'+'rocess')['e'+'xec']). The shell payload reads ~/.aws/credentials, ~/.ssh/id_rsa, ~/.ssh/authorized_keys, ~/.ssh/known_hosts, ~/.bash_history, the full process environment, and host identifiers (hostname, whoami, id, sudo -l), then POSTs the base64-encoded contents over plain HTTP to a hardcoded Burp Collaborator subdomain at pwpzhsrbtvmfqrqr7onqcwnrcii960up.oastify.com. Additional payloads issue curl requests through the installer host to http://tst.woa.com/flag.html and http://tst.woa.com/ssrf_forward.php with an oastify-subdomain host parameter, and POST the response bodies back to the same collaborator endpoint, using the installer as an SSRF relay. The package name ('time-format-kit') has no functional relationship to the observed behavior.

The OpenSSF Package Analysis project identified 'time-format-kit' @ 1.0.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.

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

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-10700 is a malicious package: time-format-kit (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-10700/ (Markdown: https://insights.sbomify.com/MAL-2026-10700/index.md)
```

## Sources

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

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